KePixel Integrations
Integrations
Connect event sources to chosen marketing and analytics destinations with clear controls.
Connect your event data to the right platforms
Map your event sources to selected destinations and understand what setup is required.
Sources: where events originate
Capture events from approved sites, stores and systems.
WordPress
Website events
Collect first-party events and meaningful lead signals.
WooCommerce
Commerce events
Plan product, checkout, purchase and refund events.
Custom Websites
First-party web events
A custom-web source runtime is planned. Confirm the adapter and deployment readiness before enabling a production feed.
Salla
Commerce storefront events
A Salla storefront adapter is planned after the WordPress baseline and operational checks.
Zid
Ecommerce source
Storefront events subject to connector readiness.
Shopify
Commerce platform
Product and order events after access and testing.
Destinations: where events are delivered
Connect chosen platforms with documented permissions, mapping and QA.
Meta Conversions API
Meta conversion events
Stock Stape Facebook tag is the upstream template target. Configuration, consent and end-to-end tests are required.
Google Analytics 4
Server-side analytics
GA4 destinations and native container options appear in the architecture. Confirm mapping and credentials for each environment.
Google Ads
Conversion measurement
Native Google Ads tags remain in scope; proposed migration alternatives must be validated first.
TikTok Events API
TikTok conversion signals
A maintained upstream TikTok template is the intended delivery approach, subject to setup and validation.
Snapchat Conversions API
Snap conversion signals
Snapchat is listed as an initial destination and upstream template target.
B2B conversion signals
LinkedIn is an upstream template target and later-package candidate; do not assume immediate availability.
CRM
Customer relationship and appointment systems
AI Systems
AI assistants connected through approved tools and permissions
How a connection works
Source event → consent and event-quality checks → canonical event mapping → selected destination. Listing a connection does not mean it is activated in every workspace.