Send Conversions with Consent Mode

If your site uses Consent Mode, follow these steps when reporting conversions via the API.

1. Include any relevant first-party identifiers. For example, if you specified CustomProfileId in the UTT's identify call, send the CustomProfileId with the conversion event.
2. After the user provides consent, use generateClickId to obtain an encoded first-party user identifier on your pages. Send this parameter with the conversion event. Follow step 3 for loyalty or rewards conversions without consent.

JavaScript

<script>
  ire("generateClickId", function(click_id) {
    console.log(click_id);
  });
</script>

1. Send all conversion events for users referred by loyalty or rewards partners along with the relevant identifiers, even if the user hasn't provided consent. To identify such conversions, check for the impact-loyalty localStorage object, or store an identifier when the user's initial navigation contains the im_rewards=1 flag in the landing page URL query string.
2. Send all conversion events even when consent is not provided. This is necessary to accurately assess partner referral impact. For non-consented users, exclude personally identifiable information (PII) such as customer IDs, emails, and click IDs from the event data.

Read more about Integrating Consent Mode on impact.com.