Review the existing source before creating another Pixel
An ecommerce manager’s implementation plan should distinguish moving a store from starting measurement anew. When migrating to ikas, review ownership, access and the existing ad-account relationship first. Changing platforms does not automatically mean that every Meta data source should be recreated.
If the existing source is legitimate and manageable, evaluate continuity. If it belongs to another business or mixes unrelated store events, document how that will be resolved. Keep a small record of source name, numeric identifier, business portfolio, ad account and authorized owner. A dataset label should be checked against the intended web source rather than treated as a naming detail.
Mark the migration date, old-store shutdown and new-store launch in reporting. Investigate overlap when both stores remain available. Removing an old agency’s access and deleting the business’s data source are different decisions. A good handover covers permissions and change responsibility as well as the identifier; it should allow the business to maintain the connection after its original installer leaves.
Connect the Pixel identifier and CAPI token separately
For a store management implementation, follow the current official ikas guide. Use Sales Channel > Extensions and the Facebook Pixel Code field for the numeric dataset ID. The Facebook Conversion API connection is configured separately with the access token. Confirm the intended channel before saving.
Do not import another platform’s app-installation or maximum-data-sharing recipe. Saving a Pixel ID does not prove that a CAPI token has been correctly connected. If a field is missing, check panel language, channel and access level. Confirm the current platform method with support instead of pasting guessed tracking code into an arbitrary theme file.
The token is a connection secret. Mask it in screenshots and keep it out of public documents and visitor-facing JavaScript. Check that the source and token belong to the same implementation. Record changes to identity, scope or credentials with a date and owner. Configuration saved and correctly interpreted events received are separate acceptance stages.
Select the source
Confirm ownership, the existing identifier and ad-account relationship.
Connect Pixel
Save the numeric ID in the intended sales-channel connection.
Connect CAPI
Use the corresponding token in its separate field and verify the connection.
Accept the data
Review shopping actions and parameters rather than relying on a saved status.
FROM READING TO A NEXT STEP
Prepare your ikas measurement handover
Define the existing source, channel connections, event acceptance tests and maintenance owner.
Check platform-specific settings and data scope
A measurement implementation should consider current platform guidance alongside the store’s lawful data scope. The Turkish ikas documentation recommends automatic website matching on and code-free automatic event tracking off. This is platform-specific advice, not a universal switch configuration for other ecommerce systems.
Record which matching information is used, under which permission conditions data is sent and whether extra automated events overlap with existing integration events. A recommendation to enable a setting is not permission to disclose personal data. The controller’s assessment of purpose, necessary parameters and lawful scope still needs to guide implementation.
Review the allowed-domain list against the actual store arrangement. Old domains, new domains, subdomains and separate channels may require additional verification. Test that the intended flow remains available. Traffic permissions, customer consent and domain ownership verification address different questions. Completing one does not replace the others or establish that all collection is appropriate.
Accept events by meaning rather than raw counts
During a checkout usability test, compare product, cart, checkout and order actions with the measurement records. Review Test Events, Diagnostics and the official browser diagnostic tool together. The extension previously known as Pixel Helper may appear as Meta Ads Data Advisor; verify the publisher and the tool’s actual scope.
Two records from browser and server do not alone prove that two purchases were counted. The technical deduplication explanation addresses matching event names and IDs. An additional sender generating distinct records in the same channel is a different issue. Inspect source details and the transaction relationship instead of classifying every apparent duplication as normal.
A cart-add action count and a unique-cart count are also different measures: one shopper can add several products. Verify order value, currency, item IDs, payment state and reload behavior. Use a safe test procedure that avoids actual shipping or customer messages, and identify test records separately in business analysis. A successful received-event status does not validate all of these meanings.
| Observed condition | Distinction to make | Next check |
|---|---|---|
| Two source records | Browser and server copies of one action? | Name, ID and deduplication details |
| Many cart actions | Actions or unique carts? | Report definition and shopping flow |
| Missing purchase | Did an order and payment actually occur? | Store record, permission and source details |
| High value | Which components enter the total? | Currency, discount, shipping and refund |
| Repeated transaction | Does reloading create another purchase? | Repeat verification on the same order |
Connect the right catalog and localization
An ecommerce consulting plan should define catalog acceptance independently. The ikas catalog document describes obtaining the Facebook Commerce Manager Catalog Connection URL from Extensions and adding it as a Meta feed. Connect the intended Pixel and inspect processing; a catalog is a different deliverable from browser event installation.
Compare an example product and variant’s event identifiers against catalog records. Price, availability, currency, image and destination should agree. After store changes, inspect the latest successful catalog update. Do not open a campaign on the assumption that every change appears instantly. Investigate outdated records or rejected items using the actual processing evidence.
The ikas localization documentation describes region-specific catalog connections. International stores should check the intended market, language and currency. A Turkish catalog paired with another market’s differently priced landing page can mislead the comparison. A catalog connection does not automatically establish access to Instagram Shop or platform-hosted checkout for your business and market.
Plan disconnection, theme changes and additional senders
Within store maintenance, define what a Pixel-removal request means. Disconnecting the native field, stopping CAPI, removing old code and deleting the Meta source are distinct operations. Turning off one connection does not establish that other senders have stopped collecting or forwarding events.
Confirm the current panel action, retain configuration evidence safely and assign a rollback owner. Manual code requires a platform-appropriate technical review. Do not present Shopify’s theme.liquid or head.liquid recipe as verified ikas instructions. Working with a second agency does not itself require another Pixel; assigning suitable permissions may address the need with less complexity.
Retest events after theme or app changes. A native connection does not guarantee that every customized shopping path is unaffected. If another data source is justified, design its purpose, data scope, catalog relationship, maintenance and permissions separately. Multiple Pixels should not be sold as a verified backup strategy or an automatic method of improving performance.
Monitor consent and reporting differences after setup
When using CAC, ROAS and MER for decisions, state the reporting period, attribution and revenue definition. The Turkish cookie decision distinguishes information from required consent. Server-side sending does not by itself make processing and transfers lawful or remove the need to assess their scope.
For processing requiring consent, test acceptance, refusal and withdrawal in both browser and server flows. Avoid unnecessary personal information in URLs or custom event labels. Hashing alone is not anonymization. Mask tokens and customer details when sharing a support case while preserving enough specific evidence to reproduce the measurement issue.
Store order reporting and Meta-attributed outcomes need not be identical. Still investigate duplicate events, wrong amounts, periods, cancellations and refunds rather than attributing every difference to modeling. Unsupported claims of a 20–30 percent CAPI performance improvement or inevitable Pixel-driven ROAS growth are not acceptance criteria. Improved measurement and incremental business sales are separate findings.
BEFORE YOU DECIDE
Frequently asked questions
Do I need a new Pixel when migrating to ikas?
Not always. Review whether the existing source belongs to the business, remains accessible and has the right scope. Check overlap between old and new stores plus catalog and ad-account relationships before choosing continuity or a different source.
Does saving the Pixel ID automatically enable CAPI?
The current official flow connects the Pixel identifier and Facebook Conversion API token in separate fields. Saving one does not prove the other is working. Verify each connection and event source; do not substitute another platform’s maximum-sharing recipe.
Are two event records necessarily duplicate counting?
No. Browser and server can send two copies of one action. Inspect deduplication evidence. Extra same-channel senders or different transaction identifiers need separate investigation. Do not assume that every increased count is expected.
Should I retest after a theme change?
Yes. Recheck actual product, cart, checkout, order and consent behavior even with native integration. Previous test evidence does not automatically cover a changed custom theme or newly installed application.
Does a second agency need a second Pixel?
First evaluate suitable roles and access to the existing business-owned source. Another installation without a clear purpose adds complexity. If required, design the separate source’s data, catalog, permissions and ongoing owner deliberately.
Why might Meta and ikas reports disagree?
Event versus cart definitions, attribution, reporting periods, currencies, payment states, cancellations and refunds may differ. Compare like definitions first, then investigate missing or repeated records. A discrepancy alone does not establish integration failure or business success.
LET’S DEFINE THE SCOPE
Prepare your ikas measurement handover
Define the existing source, channel connections, event acceptance tests and maintenance owner.
Discuss the measurement plan