Conversion tracking. Attribute every dollar to the click that earned it.

If the elido_cid query parameter is lost before the conversion event fires — due to a redirect chain, SPA router not forwarding query params, or third-party checkout stripping unknown parameters — the conversion cannot be attributed. Test the full funnel: click a short link, trace the elido_cid through every page to the checkout confirmation, verify it appears in the conversion POST. The Elido attribution snippet (a small JavaScript block) also sets the click_id in a first-party cookie as a fallback — if the URL parameter is lost but the user is still in the same browser session, attribution can recover from the cookie.

Elido does not automatically process refund events. If a Stripe charge.refunded or Shopify refunds/create event fires, Elido does not debit the attributed revenue. You can POST a negative-value conversion event to the custom endpoint to reverse attribution manually. A refund webhook listener is on the roadmap. Until then, if you need accurate net revenue in Elido, subtract refund totals using the export data and your order management system.

No — if the user clicks the short link on mobile but completes checkout on desktop, the click_id is not transferred between devices. The conversion will be unattributed unless the user's session preserved the elido_cid across the device switch (e.g., via a logged-in account that stored it). Cross-device attribution requires a server-side identity graph, which Elido does not provide. For cross-device attribution accuracy, use your MMP or CDP alongside Elido's server-side conversions.

All ISO 4217 currency codes are accepted in the value field of a conversion event. Revenue is stored in the original currency; the analytics dashboard shows revenue in the currency of each conversion event. If you need a rolled-up view in a single currency, export the conversion events and convert in your warehouse — Elido does not apply FX conversion rates.

When creating a Stripe Checkout Session, set client_reference_id to the value of the elido_cid URL parameter from the referring click. In JavaScript: const session = await stripe.checkout.sessions.create({ ..., client_reference_id: searchParams.get('elido_cid') }). Elido's webhook handler reads this field from checkout.session.completed. If you're using PaymentIntents directly, use the metadata field with key elido_cid instead. The setup guide at /docs/guides/conversion-tracking has copy-paste code for Node, Python, and Go.

Yes. Conversion events are stored in a separate ClickHouse table (conversions) alongside the click events table (clicks). Scheduled exports to S3, BigQuery, or Snowflake include both tables. The JOIN key is click_id. A reference SQL query that joins clicks to conversions and computes revenue per campaign UTM source is in the export guide.

Yes — the custom conversion endpoint accepts any event_name and an optional value (set to 0 for non-revenue events). Use event names like 'trial_started', 'demo_booked', 'form_submitted'. These appear in the link's analytics view under 'Conversions' with the event name as the label. If you also forward to GA4, these map to custom GA4 events. Conversion counts (not just revenue) are visible per-link and per-campaign regardless of event value.

Webhook receipt to ClickHouse: typically under 5 seconds via the same Redpanda pipeline as click events. Attribution (matching the conversion to the originating click) happens synchronously at webhook receipt — if the click_id resolves, attribution is immediate. Downstream forwarding to GA4 / Meta CAPI / Mixpanel is asynchronous and adds 2–10 seconds. The revenue number in the dashboard analytics view updates within 30 seconds of the conversion event being received.