Install and Verify the Tracking Script

The tracking script connects website visits to events in Konektor. Follow this order: copy the workspace code, install it on every page, open the website, and confirm that Konektor receives a real event. Ad-platform delivery is a separate, optional step.

Before you start

You need:

• owner or admin access to the Konektor workspace;
• permission to change the website header or Google Tag Manager container;
• a website page that you can open for testing;
• ad-platform credentials if you also want to send events to Meta, Google, or TikTok.

1. Copy code from the correct workspace

1. Enter the workspace that you want to track.
2. Open Website Tracking.
3. Find the Tracking code card.
4. If an ID is not available, click Create tracking code.
5. Click View code. On the Install yourself tab, click Copy Code.

Always use the complete code generated by the dashboard. Do not copy a sample ID from documentation or replace the workspace ID manually.

2. Choose one installation method

The script must load on every page that you want to track. Install it once through a method that applies site-wide.

HTML manual

1. Open the website's main layout template.
2. Paste the complete code before the closing </head> tag.
3. Save, build, and publish the website.

If the website navigates without loading a new page, make sure the app also records PageView after each route change. Ask a developer to check this when the URL changes without a full page reload.

Google Tag Manager

1. Open the website container in Google Tag Manager.
2. Select Tags > New.
3. Select Tag Configuration > Custom HTML.
4. Paste the complete Konektor code.
5. Under Triggering, select Initialization - All Pages.
6. Save, use Preview to test, then Submit to publish the container.

Make sure the Google Tag Manager container itself is installed on the website. A tag that is only saved and not published does not run for visitors.

WordPress

Konektor has no WordPress plugin of its own. Use a trusted feature or plugin that inserts code into the site-wide header.

1. Open the header-code settings in WordPress.
2. Paste the complete Konektor code into Header.
3. Save the change.
4. Clear the WordPress, caching-plugin, and CDN caches if used.

On WordPress.com, the ability to install JavaScript depends on the site's plan. See the WordPress header-code guide if you cannot find a code installation option.

Shopify

Back up or duplicate the theme before editing code.

1. Open Online Store > Themes.
2. Open the action menu for the active theme, then select Edit code.
3. Open the main layout file, usually theme.liquid.
4. Paste the complete Konektor code before </head>.
5. Click Save, then open the published storefront.

See the Shopify theme-code guide if your theme has a different structure.

Landing-page builder

Look for a setting named Custom Code, Tracking Script, Header Script, or something similar. Paste the code into the global header area, not into a single page element.

If the platform has separate public and checkout pages, check whether the code must be installed in both areas. Use the platform's official help because menu names can differ.

Custom backend app (PHP, Laravel, Node.js, and similar)

The Konektor tracking code is a plain HTML <script> tag. It does not depend on the backend language, so the same steps apply to a website rendered by PHP, Laravel, Node.js, or another framework.

1. Open the shared layout template every page uses, for example header.php or a Blade layout file.
2. Paste the whole code before the closing </head>.
3. Confirm that template is used by every route or page you want to track, including pages rendered from a different controller.

Follow the same verification steps in 3. Send and verify a website event below.

3. Send and verify a website event

Run this test on the published website, not only inside its editor.

1. Open the website in a private or incognito window.
2. Open a page that contains the Konektor code.
3. Return to the Konektor member dashboard.
4. In the Activate one thing first panel, click Check again.
5. Confirm that the website step says an event, such as PageView, was received.

The website step in the panel becomes done after the first event arrives. If the status does not change, wait a moment, then click Check again.

4. Optional: add an ad platform

Skip this section if you only need to confirm that website tracking works. Add an ad platform after the website step in the panel is done.

1. Open Website Tracking. If the code does not exist yet, click Create tracking code.
2. Click Add ad platform. The Ad platform choices include Meta, Google, and TikTok.
3. Select a platform.
4. Enter the values from that platform account.
5. Click Save.

Use these guides for credentials and event mapping:

• Meta Conversions API
• Google Ads
• TikTok Events API

By default, the Konektor script does not automatically load an ad platform's browser tag. If you already manage Meta Pixel, Google tag, or TikTok Pixel through Google Tag Manager or website code, keep the browser tag there to avoid duplicate installation.

5. Optional: test platform delivery

1. In the Connected ad platforms table, open the platform row menu, then select Test send.
2. Enter the Event Name and any required test data.
3. For Meta, enter the Test event code (Test Event Code) from Meta Events Manager > Test events. This code is required for Meta.
4. Click Send test.
5. Check the result in Konektor and the platform's test tool.

The Test passed status differs from Healthy. Healthy appears after the platform receives real events. A saved configuration does not prove that delivery works. The test result does not change the required website-tracking evidence.

Move or remove a pixel from an old workspace

One pixel ID can be in only one workspace. If the ID is still in an old workspace, Konektor offers a way to move it to the new workspace.

1. Open the new workspace, then open Website Tracking.
2. Click Add ad platform, then enter the same platform and pixel ID as the old workspace.
3. Click Save.
4. If your account is an owner or admin in the old workspace, Konektor shows the message This pixel is in the workspace {old workspace name}. Click Move to this workspace. This still works even when the old workspace has no active plan.
5. If your account is not an owner or admin in the old workspace, Konektor shows a message that another workspace already uses this pixel. Ask the owner or admin of the old workspace to do the step above, or ask them to invite your account as an admin in this new workspace.
6. After the pixel moves, replace your website tracking code with the code from this new workspace.

Notes:

• Only a workspace owner or admin can move or delete a pixel.
• Moving a pixel does not delete the leads in the old workspace.
• You can also delete the pixel directly in the old workspace. Open the row menu in the Connected ad platforms table, then select Delete. Do this if you do not want to move it.

Optional settings

Allowed domains

Use the domain list when only specific domains should be allowed to send events.

1. On the Website Tracking page, open the Allowed domains section.
2. Enter one host per line, such as example.com and www.example.com.
3. Click Save domains.
4. Test the website again.

When the list is empty, all hosts are allowed. When it contains entries, a website domain that is not listed is rejected.

Custom domain

After adding or changing a custom domain in Konektor, open Tracking code again and copy the latest code. This is safer than editing domain options inside the script manually.

Troubleshooting

If the problem continues, record the test-page URL, test time, and error message. Hide access tokens, API secrets, customer identities, and personal data before sharing screenshots.

Next steps

• Create a WhatsApp Link.
• Configure your conversion strategy.
• Review Analytics.
• Install through Google Tag Manager.
• Learn the LPWA flow from the ad click to the WhatsApp chat.