Connect Meta Pixel (Conversions API) to Elido

Elido sends conversion events to Meta's Conversions API (CAPI) server-side. This complements your browser-side pixel and improves signal quality, especially for users who block JavaScript or use iOS 14.5+ privacy restrictions.

What you need#

• A Meta Business account with a pixel.
• Access to Meta Events Manager.
• The pixel's Conversions API access token.

Step 1 — Find your Pixel ID#

1. Go to Meta Events Manager.
2. In the left panel, click Data Sources.
3. Select your pixel. The Pixel ID is the number shown at the top (e.g. 123456789012345). Copy it.

Step 2 — Generate a Conversions API access token#

On the same pixel detail page:

1. Click the Settings tab.
2. Scroll to Conversions API.
3. Click Generate access token under "Set up manually".
4. Copy the token. It's a long string starting with EAAB....

This token never expires unless you revoke it. Store it like a password. You can rotate it from the same settings page at any time.

Step 3 — Configure in Elido#

1. Go to Dashboard → Conversions → Meta CAPI → Set up forwarding.
2. Paste the Pixel ID and the access token.
3. Click Save.

Step 4 — Send a test event#

1. In Elido, click Send test event. Elido fires a Purchase test event with test_event_code: TEST1234 (or whatever code Elido generates).
2. In Meta Events Manager, go to your pixel → Test Events tab.
3. Wait up to 30 seconds. You should see the Purchase event appear.

If you see "Received" in the Test Events tab, the integration is working.

How Elido maps event parameters#

Elido field	Meta CAPI parameter
click_id	event_id (for deduplication)
conversion.value	value
conversion.currency	currency
utm_source	Custom data: source
utm_campaign	Custom data: campaign
User IP (from click)	client_ip_address (hashed before send)
User agent (from click)	client_user_agent

Meta uses event_id to deduplicate events between your browser pixel and Elido's server-side event. If both fire for the same conversion, Meta counts it once.

Event names#

Elido sends Purchase for conversion events. If you also fire AddToCart or Lead events on your site and want those forwarded, use the webhooks + custom payload option to build a custom mapping.

Privacy and data handling#

Elido hashes email and phone before sending to Meta (SHA-256, lowercase, trimmed). IP addresses are sent in plain text — Meta requires this for matching but doesn't store them beyond the matching window. Review Meta's data policy for your own compliance assessment under GDPR.

Troubleshooting#

Test event not appearing in Events Manager — Check the Pixel ID for typos. Also verify the access token is for the correct pixel — tokens are pixel-specific.

"Invalid token" error in Elido delivery log — The token was revoked or belongs to a different pixel. Regenerate from Events Manager → Settings → Conversions API.

Events showing but no attribution in Ads Manager — Attribution takes 24–72 hours to process. Also check that the client_ip_address is passing correctly — without a matching signal, Meta can't attribute to a campaign.

Double-counting with browser pixel — Make sure the event_id from your browser pixel matches the Elido click_id. If they're different strings, Meta treats them as two distinct events. See Meta's deduplication guide for the exact matching rules.