1.1 What is Advanced Matching?
Advanced Matching is a tool that helps your pixel work harder and smarter. It allows your website to securely share privacy-protected customer information with NewsBreak Ads.
This "privacy-protected" part is key: the data is scrambled (or "hashed") before it’s sent, so it stays secure while helping our system connect the dots. This improves NewsBreak Ad’s ability to match website events to people, which can increase attribution accuracy, optimization performance, and audience quality.
1.2 How it helps your business
By sharing this extra bit of secure info, NewsBreak Ads can more accurately match actions on your website, like a purchase or a sign-up, to the people seeing your ads. This is helpful for several reasons:
Better Tracking: You get a much clearer picture of which ads are actually driving sales.
Smarter Delivery: Our system learns faster, which types of people are likely to convert. So it can show your ads to the right audience.
Higher Quality Leads: It helps find more people who are similar to your best customers.
2.1 Two ways to set up Advanced Matching
NewsBreak Ads supports two implementation methods. Please choose and use only one method at a time. Using both together can cause data errors.
Option A: Manual Advanced Matching – You manually add extra data fields into your pixel code. Best for those who want full control.
Option B: Automatic Advanced Matching – The pixel detects identifiers on your site automatically. Best for a quick, "no-code" setup.
Which method should I choose?
| Feature | Option A: Manual | Option B: Automatic |
|---|---|---|
| Effort Level | High (Requires developer help) | Low (Plug and play) |
| Technical Skill | Coding and Pixel knowledge | No coding required |
| Control | Full control over specific data sent | NewsBreak Ads detects data for you |
| Speed | Takes longer to deploy | Can be enabled instantly |
| Best For | Advanced teams with custom data needs | Most advertisers wanting a quick setup |
Option A: Manual Advanced Matching
This method requires you to explicitly include identifier fields in your event code. This is the best choice if you are comfortable with Pixel Code and want total control over which specific pieces of information are sent.
To set this up, follow the step-by-step instructions under the "How to Add Extra Fields" section in our in this article.
Important: Only use this method if you are familiar with Pixel Code and want full control over which identifiers are sent.
Option B: Automatic Advanced Matching
This is the fastest way to get started and requires no code changes. The pixel will collect supported identifiers directly from your site once you turn the feature on.
How to enable:
Navigate to Event Management.
Select Web Events.
Toggle on Automatic Advanced Matching.
Note for Shopify users: If you are using the Shopify app for your pixel, your consent settings are managed directly within your Shopify site.
General Constraints
To ensure your data is accurate and effective, please follow these guidelines:
Legitimate Data: Only send data you have collected through proper, legal channels.
No Placeholders: Do not send "dummy" values or hashed placeholders.
Current Context: Data should always correspond to the user currently on the site.
Privacy First: Always respect user consent and local privacy requirements.
Additional Parameters Reference Table
The following fields may be sent for Advanced Matching. Provide as many valid fields as available to improve match quality.
| Field Name | Parameter Name | Description / Format | Hashing Required |
|---|---|---|---|
| nb_em |
Trim any leading and trailing spaces. Convert all characters to lowercase Input: John_Smith@gmail.com Normalized format: john_smith@gmail.com Expected SHA256 output: 62a14e44f765419d10fea99367361a727c12365e2520f32218d505ed9aa0f62f |
YES (SHA256) | |
| Phone Number | nb_ph |
Remove symbols, letters, and any leading zeros. Phone numbers must include a country code to be used for matching (e.g., the number 1 must precede a phone number in the United States). Always include the country code as part of your customers' phone numbers, even if all of your data is from the same country. Example: Input: US phone number (650)555-1212 e323ec626319ca94ee8bff2e4c87cf613be6ea19919ed1364124e16807ab3176 |
YES (SHA256) |
| First Name | nb_fn | Lowercase. Remove spaces and punctuation. Use the user’s real first name. | YES (SHA256) |
| Last Name | nb_ln | Lowercase. Remove spaces and punctuation. Use the user’s real last name. | YES (SHA256) |
| Age | nb_ag |
Please only pass back the ID of each range, here is the mapping:
|
No |
| Gender | nb_ge |
Please only pass back the ID of each gender, here is the mapping:
|
No |
| City | nb_ct | Lowercase city name. No abbreviations or extra characters. | No |
| State | nb_st | Lowercase state or region (use standard abbreviation when applicable). | No |
| ZIP Code | nb_zp | Postal or ZIP code for the user’s address. | YES (SHA256) |