Turtl can be combined with Microsoft Dynamics 365 (MSD365) to provide insight into how each individual reader is consuming your content. To do this, you will need to first ensure your MSD365 integration is set up and then send each reader their lead capture URL (LCURL) for your content.

1. Ensure MSD365 integration is configured for your account

This can be done by following our guide. If you are unsure or need help, please speak to your Customer Success Manager.

2. Create your email in MSD365

Use the standard Dynamics 365 email creation tools to design your email as you normally would. You can do this either in a customer journey or as a direct marketing email.

3. Insert your Turtl Doc link

To enable tracking, you’ll need to insert a personalized lead capture URL into your email. The LC URL should follow this format:

https://yourteam.turtl.co/story/doc-slug?lead[store]=dynamics&lead[id]={{contact.contactid}}

Make sure to:

Replace yourteam with your team name or subdomain.
Replace doc-slug with the slug of your Turtl Doc.
Use the MSD365 merge tag {{contact.contactid}} to dynamically insert the contact’s unique ID.
Use a Contact record. Lead Capture URLs resolve Contacts only, so a Lead ID will not be recognised.
Use the raw Dataverse GUID. The value must arrive as the ID itself, not as a formatted or encoded version of it.

For example:

https://team.turtl.co/story/meet-the-turtl-doc/?lead[store]=dynamics&lead[id]={{contact.contactid}}

This setup ensures each contact receives a unique URL tied to their Dynamics contact record.

Tip: Send yourself a test email before your first campaign and check the URL you land on. If the address still contains the token text rather than a long ID, Dynamics has not substituted it. Insert the field using the personalisation picker in the email editor (“Personalisation”, then “Audience”, then “Contact”, then search for “contactid”) rather than typing it by hand.

4. Send your email as usual

Select your recipients and send from MSD365 as usual.

5. Check your Turtl analytics

Once your recipients have started reading your content, they will appear under Contacts within Turtl analytics.

6. How cookie consent affects your results

Your readers’ cookie choices do not stop us identifying them from a Lead Capture URL, but they do affect how much of the picture you keep.

The contact ID travels in the URL itself, so no cookie is involved in identifying the reader. When the Doc loads we read the ID, look the contact up in Dynamics, and record the reader as known with their name and email. This happens whether or not the reader has responded to a cookie banner.

What a reader loses by declining non-essential cookies:

Their identity stops persisting. Their reads are not joined into a single reader profile, and if they return to the Doc later without a Lead Capture URL they arrive as a new anonymous reader.
Engagement from an embedded Dynamics form cannot be linked back to them. See Embedding a Microsoft Dynamics 365 form.

What is not affected:

Their reads are still counted. Read tracking follows your team’s analytics setting, not the reader’s cookie choice.
Personalization still works, as the reader’s company is identified from their IP address rather than a cookie.

Emailing Lead Capture URLs with Microsoft Dynamics 365