![]() ![]() You’ll notice the open pixels at the beginning and end of the HTML in the email. You can check that your delivered emails have “open pixels” added and the links wrapped, by looking at the internals of the mail (in Gmail, use the menu top-right and choose “Show Original”). Tracking-domain # Put your own domain here Configure PowerMTA to use that domain instead of the default, with.Wait a few minutes before trying this, to allow your DNS changes to propagate through the Internet, depending on your DNS provider. Register tracking domain in your SparkPost account, and verify it.You can also use HTTPS tracking domains, although this is more involved (see SparkPost configuration steps here). CNAME .spgo.io # if you have a SparkPost EU account CNAME # if you have a SparkPost US account This will usually be a subdomain of your top-level domain, e.g. Create tracking domain with your DNS provider by creating a CNAME record.If you would prefer to use your own tracking domain (this is better from a deliverability standpoint), do the following: Tracking-domain .spgo.io # this is the endpoint for SparkPost EU tracking-domainįor SparkPost EU accounts, add the following line: You specify your SparkPost numeric customer ID here’s instructions for finding it. PowerMTA’s Engagement Tracking solution defaults to the tracking domain for the SparkPost US-hosted service. You can also mark particular PowerMTA traffic to be reported as belonging to a SparkPost subaccount – this is another way to distinguish one particular traffic stream from another. You can be more selective about what traffic streams to upload if you wish. ![]() This tells PowerMTA to upload to Signals, in this case globally for all traffic (more info here, for v5.0). This tells PowerMTA the disk space threshold at which it should start to delete the oldest SparkPost JSON event files to make space for new files when disk space is running low. 11:50:57 Signals: Discovered 1 file, transferred 1 file successfully Each minute, even when there’s no traffic, you’ll see: This directive is optional and when enabled, gives a bit more info in the pmta.log file, which can be useful during setup to confirm that everything’s working correctly. This needs to match the address of your SparkPost API service, whether it’s US or EU. This is unique to your SparkPost account, it’s the value you got from SparkPost earlier. Here we’ll start with “Use Case #2”, which enables Signals for all traffic from this PowerMTA host, and enable SparkPost engagement tracking.Įngagement-tracking sparkpost # this turns on the open and click tracking in PowerMTAĬustomer-id 123 # Your SparkPost account number here The Signals configuration is described in the 5.0 User Guide section 10.1. #POWERMTA X JOB CODE#VirtualMTA setup and naming (and how this appears in your SparkPost Signals reports)įinally, there’s a “bonus feature” with code to ensure your campaign names are compatible with PowerMTA X-Job name conventions.Injection configuration, including DKIM.FBL events (Spam Complaints) and remote (out-of-band) bounces.We’ll also cover the other specific PowerPMTA setup aspects used in our Signals demo: #POWERMTA X JOB HOW TO#Review how to use meaningful names that show up well in reporting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |