Setup

What is needed for Edgetag setup and onboarding?

Edgetag can be setup in multiple ways depending on your tech stack and requirements. For detailed overview on onboarding start by selecting your path from our documentation here. If your website is headless, custom coding will be required. Afterward, you will be able to add multiple channels with us.

How do I integrate with platforms not currently supported?

We'd recommend checking Current Supported platforms first, review our supported platforms at https://docs.edgetag.io/ and confirm if your platform isn't already available.We can support any platform per your requirement. We just need to implement event tracking for your website. We have multiple ways to fire events based on user actions: we can write custom JavaScript code, use our NPM packages, configure a webhook, or use our HTTP API. - Custom Webhook Integration EdgeTag provides custom implementation through webhooks for unsupported platforms. We'll provide you with a custom webhook URL that connects to your platform. - API Integration Process Using the standard API provided by your platform, we can integrate and establish data flow between your system and EdgeTag for comprehensive tracking.

How do we set up EdgeTag for multiple international stores?

EdgeTag does support configuring international stores, we suggest the below approaches.

Subdomain Approach : Use subdomains (e.g., int.mysite.com) with your existing EdgeTag account and isolate pixels per region for different markets. Separate Instances : Create separate EdgeTag instances for different domains (e.g., .jp for Japan) to maintain complete separation between regions.

Recommended Process : Start by testing with isolated channels for each region first, then consider blending data once you've verified performance across all markets.

Is there a way to test setup on dev/staging before pushing to production?

Yes, EdgeTag supports multi-environment testing. You can create and install the EdgeTag app across all your environments including development, staging, and production. Testing Process - Install EdgeTag on your dev/staging environments - Test all tracking functionality and integrations - Verify event firing and data accuracy - Confirm setup works as expected before going live

How do I track events/users across multiple domains?

We need to have two or more separate tags active for the respective two or more domains on EdgeTag. The user ID stitching implementation should be present on the first or the primary site to ensure that the Edgettag user id is passed from one site to the other/s.

Why might there be discrepancies in EdgeTag data compared to other tracking methods?

There could be few reasons why discrepancies may occur: - The site is not completely covered in terms of website event code addition and hence user data is not captured on the site properly - There may be multiple sources firing on the same pixel causing discrepancies - Compare both sources data to server to server or browser to browser.

What should I do if EdgeTag is not initialised on certain pages like login or restricted pages?

In such cases specific addition of EdgeTag code may be required for pages where EdgeTag isn't automatically initialized upon addition of the app. (such as login pages, checkout pages, or restricted areas). Implementation Steps - Follow our documentation to properly send user data from these pages - Ensure standard events are implemented on all relevant pages - Manually add EdgeTag tracking code where automatic initialization fails - Documentation Reference Refer to our technical documentation for specific code.

What tools does EdgeTag offer to validate and debug my installation?

You can use EdgeTag Analytics page on your EdgeTag dashboard to validate and debug installation. You can also add an event validator provider. Read more on how to validate.