eventabee — Guides
OperationalGetting started
Install eventabee
Install from the Shopify App Store, grant scopes, and open the dashboard.
Read →Install the theme app embed
Enable the Theme App Embed that ships the consent banner and browser-side pixel.
Read →Verify events are flowing
Confirm server-side ingest is working before connecting destinations.
Read →Consent & privacy
Set up the consent banner
Geo-aware opt-in, opt-out, and implied modes. Appearance and copy.
Read →Privacy policy additions for eventabee
What to add to your store's privacy policy when you install eventabee.
Read →Cookie policy additions
Cookie categories and descriptions to disclose when using eventabee.
Read →Regional privacy notes
GDPR, UK GDPR, and US state laws — a plain-English field guide.
Read →Destinations
Connect Meta (Conversions API)
Set up Meta CAPI with access token, dataset ID, and test events.
Read →Connect Google (GA4 + Ads)
Send events to GA4 via Measurement Protocol and Google Ads via Enhanced Conversions.
Read →Connect TikTok (Events API)
Set up TikTok Events API with pixel code and access token.
Read →Connect Klaviyo
Forward events to Klaviyo as metric events for segmentation and flows.
Read →Connect Pinterest (Conversions API)
Send events to Pinterest's Conversions API with ad account ID and conversion token.
Read →Connect Snapchat (Conversions API)
Send events to Snap's Conversions API with pixel ID and API token.
Read →Connect Segment
Send events to Segment as a source for further fan-out.
Read →Connect PostHog
Send events to PostHog for product analytics and session correlation.
Read →Connect a generic webhook
Forward events to any HTTPS endpoint, with headers and retries.
Read →Build a custom destination
Field mapper and JSON template for endpoints that need a specific payload shape.
Read →Operations
Replay and backfill
Replay stored events to destinations after token rotation or consent upgrades.
Read →Debug a destination
Reading the event log, per-destination retries, and the dead-letter queue.
Read →How event deduplication works
Browser and server events share an event_id — destinations dedupe automatically.
Read →