Identity Resolution on TikTok: Solving the Cross-Device Tracking Puzzle (2026)

On this page
The challenge of modern attribution is not that people stopped buying.
It is that people stopped buying in a straight line.
They see an ad on one device.
They research on another.
They compare on a third.
They may click on TikTok, search on Google, visit from email, then buy later on desktop.
That is normal customer behaviour now.
But most tracking systems still struggle with it.
TikTok is especially affected because it is mobile-first.
A user may discover your brand on TikTok while scrolling on an iPhone.
They may not buy there.
They may be on a bus.
They may be at work.
They may be half watching television.
They may save the idea mentally.
Then later, they open a laptop, search your brand and buy.
Google Analytics may credit organic search.
Google Ads may credit brand search.
Shopify may show direct.
TikTok may show nothing.
This is why many advertisers think TikTok is failing.
Sometimes it is.
But sometimes the tracking is failing.
That is where identity resolution comes in.
Identity resolution is the process of connecting user actions across sessions, browsers and devices in a privacy-conscious way.
It is not perfect.
It is not magic.
It does not reveal every person.
But it can improve matching, attribution and optimisation.
In TikTok, the key tools are:
- TikTok Pixel.
- Advanced Matching.
- Events API.
- First-party cookies.
- Hashed identifiers.
- Clean event setup.
- Proper consent handling.
- Consistent event IDs and deduplication where relevant.
In this "Mega-Authority" guide, we cover:
- The problem: Cookie loss, cross-device behaviour and attribution gaps.
- The Solution: Hashed identifiers such as email and phone.
- The Match: How TikTok connects events back to users.
- The Setup: Automatic vs Manual Advanced Matching.
The goal is simple.
Give TikTok better signal.
So the platform can measure more accurately.
And optimise more intelligently.
Part 1: The Device Gap
Modern journeys are messy.
Here is a common example.
A user watches TikTok on the bus.
They see your ad.
They like the shirt.
They do not buy.
Not because the ad failed.
Because they are on a bus.
Later, they get home.
They open Chrome on a laptop.
They search your brand.
They click your site.
They buy.
What happens in reporting?
Google may claim credit.
Organic search may claim credit.
Direct may claim credit.
TikTok may receive little or no conversion credit.
The campaign looks weak.
The finance team asks why TikTok ROAS is poor.
The marketer pauses TikTok.
Then brand search drops two weeks later.
This is the attribution trap.
Why TikTok Gets Undervalued
TikTok often sits earlier in the journey.
It creates awareness.
It creates interest.
It creates product discovery.
But the purchase may happen later.
That means the platform needs a way to connect the later event to the earlier ad interaction.
Cookies can help.
Click IDs can help.
But cookies are fragile.
Browsers restrict them.
Users delete them.
Devices do not always share them.
Mobile app journeys often break them.
That is why identity keys matter.
The Cross-Device Problem
Cookies usually live in a browser.
A cookie on Safari mobile does not automatically connect to Chrome desktop.
A cookie on an iPhone does not automatically connect to a laptop.
If the user is logged in on both devices and you can pass a privacy-safe identifier, matching becomes more possible.
This is where hashed customer data helps.
Not raw personal data.
Not passwords.
Not secret spying.
Hashed identifiers.
Used properly.
With consent.
And with a clear privacy policy.
What Identity Resolution Can Improve
Better identity resolution can improve:
- Conversion attribution.
- Event match quality.
- Retargeting audience quality.
- Lookalike audience quality.
- Campaign optimisation.
- Delivery learning.
- Cross-session matching.
- Cross-device matching.
- Deduplication between Pixel and Events API.
- Confidence in TikTok performance.
But it cannot fix:
- Bad creative.
- Weak offers.
- Poor landing pages.
- Incorrect event setup.
- No consent.
- No checkout data.
- Low traffic.
- Broken pixel.
- Bad product feed.
- Unrealistic attribution windows.
Tracking improves signal.
It does not create demand by itself.
Part 2: Identity Keys
To bridge the gap, you need persistent identifiers.
Cookies are useful.
But cookies can expire, be blocked or live only in one browser.
Customer identifiers are more durable.
The most common identifiers are:
- Email address.
- Phone number.
- External ID.
- TikTok click ID.
- IP address.
- User agent.
- First-party cookie ID.
TikTok says Advanced Matching can use customer information such as email, phone number and other identifiers to better match website events to people on TikTok. (TikTok Ads Help)
Primary Key: Email Address
Email is often the strongest identifier.
Why?
Because users often use the same email across devices.
If a user enters their email during checkout, newsletter signup or account login, that email can be hashed and sent as part of the event.
TikTok can then attempt to match it to a TikTok user.
This can improve attribution.
Secondary Key: Phone Number
Phone number can also help.
Especially in ecommerce and lead generation.
If a checkout captures phone number, or a lead form requires it, it can be hashed and sent.
TikTok’s Events API documentation says email and phone are hashing-required fields for Advanced Matching. (TikTok Ads Help)
External ID
An external ID is a business-owned user identifier.
Example:
customer_123456
If you use it, it should be stable.
It should not be guessable.
It should be handled carefully.
In many implementations, the external ID is also hashed before sending.
TikTok Click ID
TikTok can append a click ID to the URL when someone clicks an ad.
This helps connect the click to later website events within the attribution window.
Click IDs are valuable for click-based attribution.
But they do not solve every cross-device case.
If the user never clicks, or switches devices later, a click ID may not be enough.
IP Address and User Agent
IP address and user agent can help with probabilistic matching.
But they are weaker.
They can change.
They can be shared.
They can be blocked.
They should not be your main identity strategy.
Use them as supporting signals.
Not the foundation.
The Identity Stack
A stronger event payload might include:
- Hashed email.
- Hashed phone.
- External ID where available.
- Click ID.
- First-party cookie.
- IP address.
- User agent.
- Event ID.
- Event name.
- Event timestamp.
- Page URL.
- Value.
- Currency.
- Content IDs.
- Order ID.
The more accurate, permitted and privacy-safe signals you send, the better the matching potential.
Part 3: Sending the Data
The principle is simple.
Send better event data.
Not just at purchase.
At every key step.
TikTok says Manual Advanced Matching should be added to each event on your website to better match customer information with people on TikTok. (TikTok Ads Help)
Events That Matter
For ecommerce:
- PageView.
- ViewContent.
- AddToCart.
- InitiateCheckout.
- AddPaymentInfo.
- CompletePayment.
- Search.
- Subscribe.
- Contact.
- Lead.
For lead generation:
- PageView.
- ViewContent.
- FormStart.
- Lead.
- Schedule.
- Contact.
- SubmitApplication.
- CompleteRegistration.
- CallClick.
- QualifiedLead where possible.
For SaaS:
- PageView.
- ViewContent.
- SignUp.
- StartTrial.
- CompleteRegistration.
- Subscribe.
- Purchase.
- Lead.
- BookDemo.
- QualifiedLead.
Why Send Data Before Purchase?
Because TikTok needs learning signals.
If you only send email on purchase, TikTok only improves matching after the sale.
But if a user logs in, starts checkout or enters an email earlier, those events can also be matched more effectively.
This improves:
- Retargeting.
- Funnel analysis.
- Optimisation.
- Learning speed.
- Audience quality.
Automatic Advanced Matching
Automatic Advanced Matching is the easier option.
TikTok says when Automatic Advanced Matching is turned on, the pixel automatically finds customer information and matches it with people on TikTok. The information is hashed and encrypted with SHA-256. (TikTok Ads Help)
Benefits:
- Easy to enable.
- No major coding needed.
- Good starting point.
- Useful for forms and checkout pages.
- Can improve matching.
Limitations:
- Less control.
- Depends on page structure.
- May miss data.
- May not capture custom flows.
- Still needs consent and privacy review.
Use it.
But do not stop there if the account is serious.
Manual Advanced Matching
Manual Advanced Matching gives more control.
It requires technical setup.
You pass customer identifiers directly in the event code.
TikTok says manual setup requires technical resources and coding experience, and recommends adding Advanced Matching code to each website event. (TikTok Ads Help)
Benefits:
- More reliable.
- More controlled.
- Can work with custom checkout flows.
- Can pass identifiers at the right moments.
- Better for serious advertisers.
Limitations:
- Requires developer support.
- Must be implemented carefully.
- Must follow hashing requirements.
- Must avoid duplicate or malformed data.
- Requires testing.
Events API
The Events API sends events from your server to TikTok.
This can work alongside the pixel.
It can improve resilience against browser restrictions.
It can send cleaner event data.
It can help with deduplication where implemented properly.
TikTok’s matching events documentation says Advanced Matching enables businesses to send hashed email and phone to better match website and app events with ads on TikTok. (TikTok Ads Help)
For serious accounts, the best setup is often:
TikTok Pixel + Events API + Advanced Matching + first-party cookies
Not one or the other.
All together.
Shopify Setup
For Shopify, the TikTok sales channel or app may support data sharing options.
Use the strongest data-sharing setting available where appropriate and compliant.
But do not assume it is perfect.
Check Events Manager.
Test events.
Check match quality.
Confirm purchase events.
Confirm content IDs.
Confirm deduplication.
Confirm value and currency.
Custom Site Setup
For a custom website, involve a developer.
The setup should:
- Capture identifiers when available.
- Normalise data.
- Hash where required.
- Send identifiers with key events.
- Use Events API where appropriate.
- Deduplicate browser and server events.
- Respect consent.
- Avoid sending sensitive data unnecessarily.
- Validate in Events Manager.
- Document the implementation.
Do not hack this together blindly.
Bad tracking can be worse than no tracking because it trains the algorithm on poor data.
Part 4: Match Rate Benchmarks
Many platforms now focus on event match quality rather than one simple universal match rate.
The idea is the same.
You want TikTok to receive enough high-quality identifiers to match events back to users.
Check TikTok Events Manager.
Look for diagnostics and match quality indicators.
Rough Benchmarks
These are practical benchmarks, not official guarantees:
| Match Quality | What It Usually Means | Action |
|---|---|---|
| Poor | Too few identifiers. Weak matching. | Enable Advanced Matching and review event data. |
| Fair | Some identifiers are sent, but gaps remain. | Add manual matching and improve checkout capture. |
| Good | Stronger data coverage. | Add Events API and check deduplication. |
| Great | Multiple strong identifiers with clean events. | Maintain, monitor and improve consent-safe coverage. |
Avoid pretending there is one universal number that applies to every account.
A logged-in ecommerce store will match better than an anonymous landing page.
A SaaS product with account creation will match better than a brochure website.
A lead form requiring email and phone will match better than a page with no form.
What Improves Match Quality?
- Email.
- Phone.
- External ID.
- First-party cookies.
- Click ID.
- Events API.
- Correct event names.
- Correct event timing.
- Clean hashing.
- Deduplication.
- Accurate value and currency.
- Consistent content IDs.
- Better login or account creation flows.
- Less browser-only tracking.
- Consent-compliant data collection.
What Hurts Match Quality?
- No email captured.
- No phone captured.
- Broken pixel.
- Missing events.
- Wrong event names.
- Duplicate events.
- Missing purchase value.
- Missing currency.
- Inconsistent content IDs.
- No Events API.
- No first-party cookies.
- Poor consent setup.
- Checkout on a different domain.
- Payment provider redirect issues.
- Users not logged in.
Match quality is not a vanity metric.
It affects learning.
Bad matching means TikTok receives fewer useful signals.
Fewer signals means weaker optimisation.
Weaker optimisation means worse delivery.
Part 5: Summary & Checklist
TikTok attribution is difficult because customer behaviour is difficult.
People do not move in straight lines.
They watch on mobile.
They buy on desktop.
They discover today.
They convert next week.
They click sometimes.
They view without clicking other times.
Identity resolution helps connect the dots.
It does not connect all of them.
Your Action Plan:
- Enable Automatic Advanced Matching in TikTok Events Manager.
- Implement Manual Advanced Matching on key events where possible.
- Use Events API for more reliable server-side event sharing.
- Monitor event match quality and attribution windows.
Here is the deeper checklist:
- Confirm TikTok Pixel is installed.
- Confirm key events fire.
- Enable first-party cookies where appropriate.
- Enable Automatic Advanced Matching.
- Add Manual Advanced Matching.
- Hash email and phone where required.
- Send identifiers on each important event.
- Implement Events API for key conversion events.
- Deduplicate pixel and server events.
- Check value and currency.
- Check content IDs for ecommerce.
- Check attribution settings.
- Check privacy policy.
- Check consent setup.
- Monitor Events Manager weekly.
Connect the dots.
But do it properly.
The Privacy Layer
Identity resolution must respect privacy.
That is not optional.
You are dealing with personal data.
Even when hashed, identifiers such as emails and phone numbers are still sensitive from a compliance point of view.
Hashing is a protection method.
It is not a magic exemption from privacy law.
You Need To Review
- Privacy policy.
- Cookie consent.
- Data processing basis.
- Platform terms.
- User consent signals.
- Regional requirements.
- Data retention.
- Data minimisation.
- Sensitive category risks.
- Partner platform settings.
This is especially important in the UK and EU.
Work with legal or compliance support where needed.
Do Not Send
Do not send:
- Passwords.
- Medical details.
- Sensitive form answers.
- Payment card details.
- Unnecessary personal information.
- Children’s data.
- Data without proper consent or lawful basis.
- Raw email or phone where hashing is required.
- Internal notes.
- Anything you would not be comfortable explaining to a regulator.
TikTok matching should be built on clean, necessary data.
Not reckless data collection.
Automatic vs Manual Advanced Matching
Use both where appropriate.
They solve different problems.
Automatic Advanced Matching
Best for:
- Quick setup.
- Basic ecommerce.
- Standard forms.
- Early-stage advertisers.
- Teams without developers.
Pros:
- Easy.
- Fast.
- Low maintenance.
- Useful improvement over basic pixel.
Cons:
- Less control.
- Can miss custom fields.
- Depends on page structure.
- Harder to debug.
- Not enough for advanced setups.
Manual Advanced Matching
Best for:
- Custom websites.
- High-spend accounts.
- Complex checkout flows.
- SaaS.
- Lead generation.
- Server-side setups.
- Accounts with developers.
Pros:
- More precise.
- More controllable.
- Better for key events.
- Better for server-side logic.
- Easier to align with CRM data.
Cons:
- Requires technical work.
- More QA required.
- Risk of bad implementation.
- Needs documentation.
- Needs privacy review.
Best Practice
For serious advertisers:
Automatic Advanced Matching + Manual Advanced Matching + Events API
This gives you the best chance of strong, clean signal.
Cross-Device Attribution Example
Let’s return to the original problem.
Without Identity Resolution
- User sees TikTok ad on iPhone.
- User clicks or views.
- User later buys on desktop.
- TikTok cannot connect the purchase.
- TikTok reports no conversion or underreports.
- Marketer pauses campaign.
- Demand drops.
With Better Identity Resolution
- User sees TikTok ad on iPhone.
- User clicks and browses.
- User enters email for discount or account.
- Email is hashed and sent with events.
- User later buys on desktop using same email.
- Purchase event includes hashed email.
- TikTok has a better chance of matching the journey.
- Reporting improves.
- Optimisation improves.
- Budget decisions become more accurate.
Not perfect.
Better.
That is the aim.
Attribution Windows
Identity resolution works together with attribution windows.
If your attribution window is too short, you may still miss delayed purchases.
If it is too long, you may overcredit the channel.
Choose windows based on buying behaviour.
Short Purchase Cycle
Example:
- Low-cost ecommerce.
- Impulse products.
- Fashion accessories.
- Beauty products.
- Food and drink.
Use shorter windows.
Longer Purchase Cycle
Example:
- High-ticket ecommerce.
- SaaS.
- B2B.
- Finance.
- Healthcare.
- Home services.
- Luxury goods.
Use longer windows where supported and appropriate.
Measure Delay
Look at:
- Time from first visit to purchase.
- Time from add to cart to purchase.
- Time from lead to sale.
- Returning user behaviour.
- Assisted conversions.
- CRM sales cycle.
- Platform attribution reports.
- GA4 path data.
Set attribution windows based on real journeys.
Not guesswork.
Events API and Deduplication
If you run both Pixel and Events API, you must avoid double counting.
The same purchase may be sent twice:
- Browser event.
- Server event.
That is normal.
But the system needs a way to know they are the same event.
This is usually done with an event ID.
Example:
event_id = order_12345_purchase
The browser and server send the same event ID.
TikTok can then deduplicate.
If you do not deduplicate, reported conversions can inflate.
That makes performance look better than it is.
Then bidding decisions become risky.
Deduplication Checklist
- Same event name.
- Same event ID.
- Same timestamp logic.
- Same order ID where appropriate.
- Same value and currency.
- Browser event fires once.
- Server event fires once.
- Test in Events Manager.
- Check duplicate warnings.
- Monitor purchase count against backend.
Your backend order count is the truth.
Platform reporting should be compared against it.
Ecommerce-Specific Setup
For ecommerce, identity resolution is only one part of the setup.
You also need clean commerce events.
Required Event Data
Send:
- ViewContent.
- AddToCart.
- InitiateCheckout.
- CompletePayment.
- Value.
- Currency.
- Content IDs.
- Quantity.
- Product details where appropriate.
- Order ID.
Catalog Matching
If using TikTok catalog or dynamic product ads, content IDs must match the catalog.
TikTok’s catalog match rate documentation says event content_ID should follow the same format as the SKU ID in the catalog for supported event types. (TikTok Ads Help)
This matters.
If your event sends:
SKU-123
but your catalog uses:
123
matching can fail.
Fix the format.
Ecommerce Checklist
- Pixel installed.
- Events API enabled.
- Advanced Matching enabled.
- Purchase event fires once.
- Value correct.
- Currency correct.
- Order ID correct.
- Content IDs match catalog.
- Deduplication working.
- Event match quality monitored.
Lead Generation Setup
For lead generation, the purchase may not happen online.
The form submit may be only the first step.
You need to track deeper funnel quality.
Events To Send
- ViewContent.
- FormStart.
- Lead.
- Schedule.
- Contact.
- QualifiedLead.
- ApplicationSubmitted.
- Offline sale where possible.
CRM Matching
If a lead later becomes a sale, you should connect CRM data back into ad platforms where possible.
TikTok optimisation improves when it knows which leads are actually valuable.
A lead form filled by a student is not equal to a lead from a serious buyer.
If all you send is "Lead", TikTok optimises for lead volume.
If you send qualified lead or sale events, TikTok can optimise toward quality.
Lead Gen Checklist
- Capture email.
- Capture phone where appropriate.
- Hash identifiers before sending where required.
- Send lead event.
- Import qualified lead events if possible.
- Track CRM stages.
- Exclude existing customers.
- Monitor lead quality by campaign.
- Avoid sensitive data.
- Review consent.
Final Rule
TikTok does not fail just because the dashboard underreports.
And it does not succeed just because the dashboard overreports.
You need clean tracking.
You need better identity signals.
You need realistic attribution windows.
You need backend validation.
You need privacy-safe implementation.
Advanced Matching and Events API will not make every sale visible.
But they can make the picture clearer.
And in paid media, a clearer picture means better decisions.
Next Best Step
Where to go from here

About the Author
Performance marketing specialist with 6 years of experience in Google Ads, Meta Ads, and paid media strategy. Helps B2B and Ecommerce brands scale profitably through data-driven advertising.
Need this implemented for you?
Read the guide, or let our specialist team handle it while you focus on the big picture.
Get Your Free Audit