Skip to Content
Elido is in closed beta — APIs are stable but rate-limits and quotas may change before GA. Request access →
GuidesConversion tracking

Conversion tracking

A pixel tells you that a click happened. A conversion tells you the click made you money. Elido ingests Stripe and Shopify webhooks, ties each order back to the originating short link, and surfaces revenue in the same dashboard as your click totals.

The flow is:

  1. Add a webhook endpoint at Stripe or Shopify pointing at Elido.
  2. Tag your checkout sessions / orders with the elido_link_id of the link that brought the customer in.
  3. Read attributed conversions from the API.

1. Configure the webhook secret

Each provider gives you a signing secret when you create a webhook endpoint. Store both via the pixels endpoint (it doubles as the secrets vault):

curl -X PUT \ https://api.elido.app/v1/workspaces/1/pixels \ -H "Authorization: Bearer $ELIDO_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "stripe_webhook_secret": "whsec_a1b2c3...", "shopify_webhook_secret": "shpss_a1b2c3..." }'

Webhooks without a configured secret return 401.

2. Point the provider at Elido

In your Stripe Dashboard add an endpoint:

URL: https://api.elido.app/v1/workspaces/1/conversions/stripe Events: checkout.session.completed, payment_intent.succeeded

In Shopify, add an orders/paid webhook:

URL: https://api.elido.app/v1/workspaces/1/conversions/shopify Format: JSON Topic: Order paid

Elido verifies signatures (Stripe-Signature and X-Shopify-Hmac-Sha256 respectively) using the secret from step 1 and rejects mismatches with 401.

3. Tag checkout sessions

Send the originating link_id along with the order so Elido can attribute revenue.

Stripe

Set either metadata.elido_link_id or client_reference_id when creating the checkout session:

await stripe.checkout.sessions.create({ mode: "payment", line_items: [...], success_url: "https://example.com/thanks", cancel_url: "https://example.com/cart", metadata: { elido_link_id: "42" }, });

Shopify

Use note attributes - populate it on the cart from the storefront:

{% comment %} populate from a URL param like ?elido=42 {% endcomment %} <input type="hidden" name="attributes[elido_link_id]" value="{{ elido_id }}">

Elido looks for note_attributes[].name == "elido_link_id" and pulls the corresponding value.

If the link_id is missing the conversion still ingests but with no attribution - link_id and campaign_id are stored as null.

4. Read conversions

curl 'https://api.elido.app/v1/workspaces/1/conversions?limit=50' \ -H "Authorization: Bearer $ELIDO_TOKEN"
{ "conversions": [ { "id": 4711, "platform": "stripe", "external_id": "cs_test_a1b2c3", "link_id": 42, "campaign_id": 7, "revenue_cents": 4900, "currency": "USD", "customer_email": "[email protected]", "converted_at": "2026-05-01T12:00:00Z" } ], "limit": 50, "offset": 0 }

Pagination is limit (≤100, default 50) + offset. Summary cards:

curl https://api.elido.app/v1/workspaces/1/conversions/summary \ -H "Authorization: Bearer $ELIDO_TOKEN"
{ "total_revenue_cents": 1234500, "currency": "USD", "count": 211, "average_order_cents": 5851 }

What gets attributed

When a webhook arrives, Elido reads the elido_link_id from metadata / note attributes and:

  • Stores it on the conversion as link_id.
  • Looks up the link’s campaign_id and stores that too - campaign attribution is derived, you don’t tag campaigns separately.
  • De-duplicates on (workspace_id, platform, external_id) so retried deliveries don’t double-count.

There’s no UI tagger today - you have to populate the metadata yourself in the checkout integration. Most teams capture the ?elido=... URL param on landing and replay it into the checkout.

Server-side click events (Meta CAPI, TikTok Events API)

Separately from conversions, Elido can send every click on your short links to Meta and TikTok from its own servers, with no splash page in between. Each click becomes:

  • Meta Conversions API: one PageView (Graph API v24.0, action_source: website, event_source_url = the link destination, event_id for deduplication, client_ip_address, client_user_agent).
  • TikTok Events API 2.0: one ViewContent (event_source: web, page.url = the destination, event_id, user.ip, user.user_agent).

These are click events. Purchases and leads are not forwarded, and no fbc/fbp click ID is set.

Save the tokens in Settings → Pixels → Server-side events, or via the API. Tokens are encrypted at rest and never returned in plain text (the response carries meta_capi_token_masked / tiktok_access_token_masked). Omitting a field keeps its saved value; "" clears it.

curl -X PUT \ https://api.elido.app/v1/workspaces/1/pixels \ -H "Authorization: Bearer $ELIDO_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "meta_pixel_id": "1234567890123456", "meta_capi_access_token": "EAAB...", "meta_test_event_code": "TEST12345" }'

POST /v1/workspaces/{ws}/pixels/test with {"platform": "meta"} (or "tiktok") sends one test event carrying the saved test event code and returns the platform’s answer (ok, error, platform_response). Real clicks never carry the test code.

Privacy and match quality. The visitor IP is shortened to its network (/24 for IPv4, /48 for IPv6) before Elido stores or sends it, so Meta and TikTok match fewer visitors than they would with a full IP. With the workspace’s no-personal-data mode on, neither the IP nor the user agent is sent; TikTok still receives the event, Meta events are skipped because Meta rejects website events without them.

Delivery. Events are fire-and-forget: a 5-second timeout per call, at most 64 calls in flight per click-ingester, and no retries. A click that is redelivered from the event log keeps the same event_id, so the platform drops the duplicate. If the same link also shows the conversion splash with the browser pixel, Meta receives a second, browser-side PageView for the splash page; the two are not deduplicated.

Endpoint reference

MethodPath
GET/v1/workspaces/{ws}/pixels
PUT/v1/workspaces/{ws}/pixels
POST/v1/workspaces/{ws}/pixels/test
GET/v1/workspaces/{ws}/conversions
GET/v1/workspaces/{ws}/conversions/summary
POST/v1/workspaces/{ws}/conversions/stripe
POST/v1/workspaces/{ws}/conversions/shopify