Conversion tracking lets you attribute completed orders back to ID.me verification events. When enabled, the button widget mints a unique identifier when the button is rendered (or clicked, for popup flows), passes it through the verification flow as conversion_tracking_id, and stores it in a first-party cookie so you can include it with conversion events on your order confirmation page.
Add data-conversion-tracking="true" to your button widget:
Consent gating. If you need to defer tracking until the user has accepted cookies, set data-conversion-tracking to the name of a global function that returns a boolean. The widget calls it at bind time and fails closed (no tracking) if the function is missing, throws, or returns anything other than true.
On your order confirmation or thank-you page, include the conversion tracking SDK and call idmeConversion.track():
The SDK reads the idme_ctid cookie that was set when the user clicked the button, attaches it to the event as conversionTrackingId, and posts the envelope to ID.me. If no cookie is present (e.g., the user did not arrive via a tracked ID.me button), the call is a safe no-op.
Only include idme-conversion-tracking.js on confirmation/thank-you pages. The button widget handles cookie creation on pages where the button itself is rendered.
The SDK wraps your call in an envelope that matches the Order Completed v1 schema. You only supply the event name and properties; the SDK fills in eventId, timestamp, context, and the conversion ID.
Additional properties are accepted and forwarded.