WordPress plugin troubleshooting

Issue: If another plugin or your existing GTM setup is already sending ecommerce events, the Stape plugin may use identical event names. This can cause Web GTM tags to fire twice for a single action, resulting in inflated data reporting.

Solution: To resolve this, navigate to the plugin's Data Layer tab and enable the Decorate dataLayer event name option. This will append _stape to Stape event names (for example, purchase_stape, add_to_cart_stape). You can then update your Stape tags and triggers to reference these unique names. You may then choose to either keep your existing setup active for legacy events or pause those tags.

For more information on event names and payloads, see our WordPress plugin dataLayer documentation.

Issue: You have enabled Custom Loader or Cookie Keeper in the WordPress plugin settings, but the features aren’t functioning correctly.

Solution: Simply enabling Custom Loader or Cookie Keeper within the plugin settings isn’t sufficient on its own. To ensure these features function correctly, please first enable the corresponding power-up within your Stape container, and then activate it in the plugin settings.

Cookie Keeper and Custom Loader work only when the server container is hosted on Stape. Cookie Keeper also needs a paid Stape plan.

Issue: The Send test webhook feature triggers a request directly from WordPress, rather than a site visitor's browser, which is why it typically won't appear in the Server GTM (sGTM) Preview.

Solution: To view these test webhooks in the sGTM Preview, follow these steps:

1. 1.
   Open Preview in your sGTM container.
2. 2.
   Enable the sGTM Preview header config power-up in your Stape container and follow the setup instructions.
3. 3.
   Click Send test webhook in the plugin.
4. 4.
   You should now see the request appear in the sGTM Preview.

Issue: You’re noticing that tracking data fails to match across platforms like Google Ads or Merchant Center, despite the Stape plugin being configured.

Solution: The plugin generates the items array directly from your WooCommerce product catalog. If your external platforms (such as Google Ads or Merchant Center) use different product identifiers, the tracking data can’t be synchronized (for example, a mismatch between the data layer item_id and the Merchant Center id attribute). To resolve this, adjust your item_id directly in the Advanced Data Layer Settings:

1. 1.
   In the item_id mapping section, configure the identifier format to match your Google Merchant Center or external feed:

• Prefix – add a prefix if required by your feed (for example, wordpress_).
• Data Points – choose the product identifier components (for example, Country / Market code, Product ID, Variant ID, SKU, Barcode(GTIN), or Metafield). You can combine up to 3 data points.
• Separator: Set a delimiter between data points (for example, _ ).

2. Click Save.