Addressable Anonymous
Reach and engage users without a primary key with Addressable Anonymous feature.
Overview
Brands collect user data at various touchpoints such as store visits, websites, or offline events. Often, they get only a mobile number or email, but not both. These users cannot be linked to an existing profile because a primary key (PK) (like email, UID, or customer ID) is missing. This feature is supported for the following channels: Email, SMS, WhatsApp, App push, and Web push.
Note
This feature is currently in beta. To enable it, contact your account manager.
With the Addressable Anonymous feature, these users:
- Can still be stored and targeted using campaigns and journeys.
- Are marked as anonymous until a matching primary key is provided later.
- Can be merged with existing profiles when a primary key becomes available.
Example: A user enters a store and only provides his/her mobile number. With Addressable Anonymous, you can still send them SMS campaigns, even before they create an online account or share an email.
Key Concepts
- Addressable Users: Users with identifiable data like email, mobile, or CUSTID.
- Anonymous Users: Users who haven’t shared any addressable data yet but may still trigger events such as anonymous browsing or cart activity).
Benefits
- Helps brands collect and act on partial data (just email or mobile).
- Expands the reach of campaigns and journeys without waiting for full profile info.
- Ensures profiles are accurately merged when full data becomes available.
- Avoids loss of valuable offline or guest-user data.
Use Cases
Retail
Use Case: Reaching In-Store Customers Without Email
Scenario: Customers visiting a physical store often share only their mobile numbers. Email IDs are mostly collected online.
Need: Reconnect with these in-store shoppers through mobile, even if their email isn’t available.
Why It Matters: It helps you engage a large chunk of walk-in customers who might otherwise slip through the cracks.
E-commerce
Use Case: Bridging Mobile and Email-Driven Systems
Scenario: Customers log in or check out using their mobile number, but loyalty programs or CRM systems rely on email as the main identifier.
Need: Recognize and engage these users by linking mobile activity to your email-based systems.
Why It Matters: You get a complete view of the customer journey and can run unified campaigns across channels.
BFSI (Banking, Financial Services, Insurance)
- Use Case: Lead Nurturing Without Full Details
- Scenario: Leads are captured with just an email or mobile number, without full KYC details like PAN or ID.
- Need: Start engaging these leads right away, even before you have a verified primary key.
- Why It Matters: Accelerates your lead nurturing pipeline by not waiting for full data collection.
D2C / E-commerce
- Use Case: Engaging Guest Checkout & Mobile-Only Users
- Scenario: Some users check out as guests or sign up using only a mobile number, skipping email or UID registration.
- Need: Identify and reach out to these mobile-only users post-purchase or post-visit.
- Why It Matters: You recover users who would otherwise remain anonymous or unreachable.
Hospitality
- Use Case: Multiple Touchpoints, Incomplete Data
- Scenario: Users connect via Wi-Fi or register at a kiosk using just their email, and the mobile number (primary key) isn’t captured.
- Need: Communicate with them using whatever info you have—email, web cookies, etc.
- Why It Matters: Saves high-intent users from being lost due to missing a single identifier.
Media / Edtech
- Use Case: Capturing Web Message Responses Without UID
- Scenario: Visitors respond to web pop-ups or messages, sharing email or mobile, but no UID is generated.
- Need: Still track and retarget these users based on their engagement.
- Why It Matters: Helps you reach users who show interest, even if they don’t fully register.
Data Sources to Get Anonymous Data
You can capture anonymous user data from various sources, even when a primary key like email or mobile is missing. Refer to the given table to know more.
Source | Type | Description |
---|---|---|
Web JS (Form JS & Web Message) | Web | Captures anonymous data submitted through web messages (email or mobile). Collects anonymous user info via FORM.js. PK is not required. You only need to pass a mobile or email ID and a anonymous profile will automatically be created. Refer to this document to know more. |
SDK (Profile Push & In-App) | Mobile/App SDK | Collects anonymous user info via profile pushes or in-app message interactions. When users engage with in-app messages, the SDK captures those actions to enrich their profile and behavior history. - iOS SDK Documentation - Android SDK Documentation |
CSV Upload | File Upload | Upload user data with or without PKs; the system auto-matches if data overlaps. Refer to this document to learn how to upload contacts via CSV. |
Add Contact API | API | Add anonymous or identified users via single or bulk API calls. Refer to this document to know more about Add Contact API. Note: The Add Contacts API will be available mid-June onwards. |
Cloud Storage | Cloud Integration | Sync anonymous user data files from storage platforms like Amazon S3. |
Activity API | API | Capture user activity from external systems, even without a primary key. Note: Our team is working on the Activity API. We will inform you as soon as it is available for use. |
Important Points to Remember
- If you do not have a primary key, but have email/mobile information, you can still onboard users into CE via CSV/API.
- Profiles can still be targeted using email or mobile ID as addressable identifiers (instead of CUSTID).
Navigation
Follow the given steps to locate the Anonymous users section.
- Log in to your Netcore CE dashboard and navigate to Audience.
- Click All contacts. On the All contacts screen there are two sections: Identified and Anonymous.
Under the Anonymous section, unique system ID [GUID (Globally Unique Identifier)]is assigned to the users because no primary key like email or mobile number is available.

View and Manage Anonymous Users
Access detailed logs that provide insights into the activities and updates related to each contact, helping you track interactions and changes over time. Refer here to know more about Contact Logs.
Refer to these documents to know more about Audience and All Contacts.
Profile Behavior Summary
Here is how Netcore handles data without or with inconsistent primary keys:
Scenario 1: Primary Key is Email
- If only mobile is received → a new anonymous profile is created.
- If both email and mobile match → profiles are merged.
- If email differs → new profile is created.
- If existing profile is updated with a new mobile, the old one is overwritten.
Scenario 2: Primary Key is Mobile
- If only email is received → a new anonymous profile is created.
- If both mobile and email match → profiles are merged.
- If mobile differs → new profile is created or old one is overwritten.
Scenario 3: Primary Key is Customer ID
- Without Customer ID, even if email/mobile exists → anonymous profile is created.
- Providing Customer ID later with matching email/mobile → merges anonymous profiles.
- Providing Customer ID with new email or mobile → updates existing profile.
Impact Areas
-
Summary Reports: No changes will be made.
-
Detailed Reports: Four columns will now be available : Primary Key (PK), GUID, Email, and Mobile.
Note: An additional column will be included in your detailed reports across all push channels—Email, SMS, WhatsApp, App Push, and Web Push. Click here to view a sample report. -
Segmentation: You can now include both Identified and Anonymous users in a segment.
Note: Click on any profile to view the unified view of that particular profile

View Identified & Anonymous users when creating a Segment
- Reachability Count: The user count includes both identified and anonymous users, but we do not show bifurcation.
Opt-out and Blacklisting Behavior for Anonymous Users
- Email Channel
Anonymous users who receive email communications can be blacklisted based on the following triggers:
- Unsubscribe action: If an anonymous user unsubscribes from an email, the associated email address will be blacklisted.
- Spam complaint: If the email is marked as spam, the system blacklists the email.
- Hard bounce threshold: If the email crosses the configured hard bounce threshold, it is blacklisted.
Once blacklisted, email communications to that address will be halted; even if the user remains anonymous.
- SMS Channel
The system provides flexibility in handling anonymous users on the SMS channel via the UI on the anonymous listing screen:
- Blacklist Options: You can choose to blacklist either the mobile number or the associated email.
- Mobile selected: SMS will not be sent to that mobile number going forward.
- Email selected: Email communication will be blocked instead.
- WhatsApp Channel
If an anonymous user receives a WhatsApp message and chooses to opt out:
- The opt-out is recorded in the Netcore CPaaS dashboard.
- CPaaS sends an event to Netcore CE indicating the Data Profile (DP) has opted out.
- Netcore CE drops further communications to that anonymous profile on WhatsApp.
This ensures real-time enforcement of user preferences across systems.
- Profile Merging
When an anonymous profile is later identified and merged into a known user profile:
- If the anonymous profile was blacklisted, the blacklist status is carried forward to the identified profile.
- This ensures past user preferences are respected.
- However if the user re-opts in (through an offline or re-subscription method), the system allows you to whitelist the profile using that verified intent.
FAQs
Q1: Will anonymous users be blacklisted if they unsubscribe from email?
A. Yes, if an anonymous user unsubscribes, marks the email as spam, or the email hard bounces repeatedly, their email will be blacklisted automatically.
Q2: Can we stop SMS to anonymous users?
A. Yes. On the anonymous user listing screen, you can choose to blacklist either the mobile number or the email. If you select mobile, SMS won’t be sent to that number.
Q3: What happens if an anonymous user opts out on WhatsApp?
A. Their opt-out is recorded in CPaaS. CPaaS notifies CE, and all future WhatsApp messages to that profile are stopped.
Q4: If an anonymous user gets identified later, does the blacklist status stay?
A. Yes. If an anonymous user was blacklisted earlier, the blacklist status remains even after they are identified. Their preference is honored.
Q5: Can a blacklisted user receive messages again if they opt-in later?
A. Yes. If the user opts in through an offline or verified channel, you can whitelist them to resume communication.
Updated 2 days ago