Configuring email providers for recipient tracking
Connect your email tool and map dynamic tags to ensure accurate timer personalization.
3 min read
Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.
Functionality of the provider selector
The selector provides a setup guide and the necessary tag syntax. It does not integrate with your mailing list, create custom fields, or send newsletters on your behalf. Your sending platform must perform the tag replacement with actual data during the final send.
Use your platform’s personalization menu or the provided recipe to verify syntax. Editor previews may not always substitute recipient tags correctly. If a copied URL contains literal braces or percent signs, it may be a template rather than the final recipient URL.
Handling recipient identification
- Mailchimp: the recipe uses *|UNIQID|* for the stable recipient ID and *|FNAME|* for first-name personalization.
- ActiveCampaign: the recipe uses %CONTACTID% for identity and %FIRSTNAME% for first name.
- ConvertKit: the recipe uses subscriber.id and subscriber.first_name in its template syntax.
- Klaviyo, GetResponse, AWeber and HubSpot: follow the generated countdown_id custom-field recipe; do not assume a ready-made opaque ID exists in every account.
- SendGrid dynamic templates: provide countdown_id, first_name, full_name and any used custom1/custom2 values in dynamic_template_data.
- Kickpages: tag syntax depends on the connected email sender. Insert verified tags from that sender’s personalization menu; no universal Kickpages recipient tag is assumed.
Configuring custom fields
- 1Create a countdown_id field in your sending platform if the recipe mandates it.
- 2Populate this field with a unique, opaque value for every recipient and ensure this value remains stable across future emails and clicks. Do not use the same test value for all contacts.
- 3Create custom1 and custom2 fields only if your artwork requires them. Populate the corresponding name fields if you intend to use name personalization.
- 4Send a test email to at least two contacts with unique IDs, then inspect the resulting image and link URLs. Confirm all tags were replaced and that each recipient is assigned their own unique session.
Addressing URL encoding and missing data
Avoid including raw email addresses or sensitive data directly in public URLs. Ensure URL query values are encoded properly; use the provided generated HTML instead of manually concatenating unescaped values that contain spaces or ampersands.
If a field is empty, fix the contact data or discontinue the use of that field. Simply guessing a tag name does not create a corresponding field. maintain a concise, provider-specific test checklist for your team to use before every live send.