ARBook a Demo
Developer documentation

KePixel for WordPress & WooCommerce

Install the official KePixel plugin, copy the personalized connection values from this exact source Setup page, and let the plugin collect supported WooCommerce events through the KePixel first-party path.

1 · Download plugin from Setup
↓
2 · Install + activate in WordPress
↓
3 · Paste source connection values
↓
4 · Save + verify in KePixel

Implementation flow

Open your exact WordPress source

Go to KePixel → Sources → your WordPress / WooCommerce site → Setup. Values are source-specific; never copy them from another website.

Download the plugin shown in Setup

Use Download plugin on the source page. Do not rely on an old ZIP or a version copied from another project.

Install and activate it

In WordPress open Plugins → Add New → Upload Plugin, upload the KePixel ZIP, install, then activate.

Open Settings → KePixel Tracking

Enable KePixel and paste the personalized connection values shown in KePixel Setup. These values identify the workspace/site/source/runtime; they are not destination credentials.

Save and verify

Save the WordPress settings, perform a real test action, then return to KePixel Overview → Refresh source status.

KePixel → Sources → WordPress source → Setup

What KePixel Setup shows

Use the values exactly as displayed. If any field says Waiting, do not invent it; refresh the source after provisioning finishes.

Web GTM Container IDManaged by KePixel
Workspace IDSource-specific
Client IDTenant-specific
Site IDWebsite-specific
Source IDWordPress source-specific
Runtime Binding IDManaged runtime binding

What you do not need

No Server GTM edit access, destination tokens, Meta/TikTok/Snap credentials, API secrets or Cloud Run URLs belong in WordPress. KePixel keeps destination/server credentials outside the plugin.

Plugin installation

  1. Download the exact plugin ZIP from KePixel Source Setup.
  2. WordPress Admin → Plugins → Add New → Upload Plugin.
  3. Install and activate.
  4. Open Settings → KePixel Tracking.
  5. Enable KePixel and paste all connection fields shown in Setup.
  6. Save settings.

The WordPress integration uses the first-party /kpx/ route family. Do not change or proxy those paths manually unless KePixel documentation for your source explicitly requires it.

WordPress / WooCommerce event contract

EventQuality requirement
page_viewPage context from the installed site.
view_itemCommerce items; item identity should be stable.
add_to_cartConfirmed WooCommerce cart mutation + items.
begin_checkoutitems, currency, value.
purchaseConfirmed order + stable transaction_id, items, currency, value.
refundConfirmed refund tied to the original transaction_id.

Do not duplicate plugin events manually

If the KePixel plugin already emits a supported WooCommerce event, do not add a second custom script for the same event. Duplicate browser/server signals must keep the same business identity for deduplication.

Quality and customer identity

The plugin may use WooCommerce customer/order data that already exists in the store when the source contract allows it. Billing values have priority; equivalent shipping/profile values may be used only as safe fallbacks when the billing value is empty. Keep product IDs, order IDs, currency and values accurate.

No manual hashing field

Do not create extra WordPress fields for hashed email/phone just to feed KePixel. The source plugin owns its approved customer-data contract and KePixel handles destination-specific transformations downstream.

Testing checklist

  1. Plugin is active.
  2. Every Setup value is pasted exactly once.
  3. WordPress Settings → KePixel Tracking saves without an error.
  4. Trigger a product view, add to cart, checkout or test order as applicable.
  5. For purchase, verify the real order/transaction ID and totals.
  6. Return to KePixel and refresh the source status.