Tracking Platforms Reference
How conversions reach EmailElement
EmailElement asks the platform for conversions on a schedule, using the API key, affiliate URL and affiliate ID stored on the integration. The platform sends nothing to EmailElement.
A conversion is matched back to the contact by the {SubId} replacement tag, so that tag has to be
in the link the recipient clicked. See Conversions.
The five platforms
| Platform | Page |
|---|---|
| Cake | Cake |
| Everflow | Everflow |
| HitPath | HitPath |
| RedTrack | RedTrack |
| Tune | Tune |
What each one needs
All five take the same three credentials, whatever their own wording for them:
| Field | What it is |
|---|---|
| API Key | The key that lets EmailElement read your conversions |
| Affiliate URL | Your tracking domain on that platform |
| Affiliate ID | Your account or affiliate identifier |
The label on the affiliate ID field changes to match the platform you picked, so it reads the way that platform words it.
Conversion flow
Recipient clicks a link carrying {SubId}
-> the platform records the click and, later, the conversion
-> EmailElement asks the platform for conversions on its schedule
-> the conversion is matched on {SubId} and appears in Contact History
Related pages
- Conversions — the
{SubId}tag and where conversions appear - Platform Integrations — setting one up