Overview
Audience Manager lets you manage SmartNews users who have a history of interacting with your ads or products. You can use it to create custom audiences for retargeting or increasing app engagement.
There are two main ways of creating custom audiences:
- Creating audiences from website events (web activity)
- Creating audiences from ad interactions (ad engagement)
Each ad account can hold up to 50 custom audiences.
Choosing an audience type
When choosing an audience type for retargeting SmartNews users, you have two main options. You can focus on users who have already engaged with your website—such as those who have added products to a shopping cart or made purchases. Alternatively, you can target a broader pool of users who have shown interest by interacting with your ads.
SmartNews custom audiences let you serve relevant ads to users who have shown interest in your products or services, helping you focus your advertising budget on those most likely to convert.

Web activity audiences
SmartNews users who visited your website or completed specific actions can be grouped into web activity audiences.
- A custom audience can have up to 50 rules to define it. They need at least one rule to be created.
- It can take between 24 and 48 hours for a web activity audience to be ready for use.
Supported events
Pixel tags let you use the following events as rules for defining your custom audience.
Event | Description |
---|---|
Purchase | Triggered when a user fires a “Purchase” event |
Add to cart | Triggered when a user adds a product to their shopping cart |
Initiate checkout | Triggered when a user begins the checkout process |
Submit form | Triggered when a user submits a form |
Subscribe | Triggered when a user subscribes to a paid service |
Complete registration | Triggered when a user completes user registration |
Contact | Triggered when a user fires the “Contact” form submission event |
Signup | Triggered when a user fires a signup event |
View content | Triggered when a user views a details page |
Add payment info | Triggered when a user adds their payment info |
Add to Wishlist | Triggered when a user adds a product to their Wishlist |
Visit cart | Triggered when a user views their shopping cart |
Customize product | Triggered when a user fires a “Customize product” event |
Search | Triggered when a user fires a “Search” event |
Booking | Triggered when a user fires a “Booking” event |
Download | Triggered when a user fires a “Download” event |
Start trial | Triggered when a user begins a free trial |
Share | Triggered when a user fires a “Share” event |
Login | Triggered when a user fires a “Login” event |
Donate | Triggered when a user fires a “Donate” event |
Find location | Triggered when a user fires a “Find location” event |
Time spent | Triggered when a user spends enough time on a page |
Page view | Triggered when a user views a page with a Pixel base code installed |
Create a web activity audience
1Select the Audiences tab

2Select Create custom audience and select Web activity, followed by Next.

3Name your custom audience.
4Select your Pixel, site URLs, event types, and event window (7, 14, 30, 60, or 90 days). Up to 20 URLs can be added using OR logic (all URLs entered will count towards the audience).
5You can broaden (OR) or narrow (AND) your audience definition by adding additional rules (up to 50).

6Choose whether or not to refresh your audience automatically. This is disabled by default.
7When you’re happy with your audience rules, select Create audience at the bottom of the screen.
Note
- If a custom audience isn’t part of any campaign, it will stop being refreshed automatically after 30 days.
- Each audience rule can have up to 20 event types and 20 URLs.
- Website URLs use prefix matching. You can include multiple pages with the same opening URL scheme.
- Ad accounts must have a registered Pixel to use Pixels to define custom audiences.
Ad engagement audiences
Ad engagement audiences are made up of people who have a history of interacting with your ads on SmartNews.
These audiences can be assigned to your ad groups and are made up of users who wither clicked, viewed your ads (viewable impressions), or produced a conversion event (CV).
- As with web activity audiences, a single custom audience can have up to 50 rules. They need at least one rule to be created.
- It can take between 24 and 48 hours for an ad engagement audience to be ready for use.
Supported events
Ad engagement audiences support the following ad types and events:
Ad types | Events |
---|---|
Image ads only | • Clicks • Impressions (viewable) • Conversions |
Create an ad engagement audience
1Select the Audiences tab

2Select Create custom audience and select Ads engagement, followed by Next.

3Name your custom audience
4Select ad groups which will use this audience, your action type, and event window (7, 14, 30, 60, or 90 days).
5You can broaden (OR) or narrow (AND) your audience definition by adding additional rules (up to 50).

6Choose whether or not to refresh your audience automatically. This is disabled by default.
7When you’re happy with your audience rules, select Create audience at the bottom of the screen.
Note
- If a custom audience isn’t part of any campaign, it will stop being refreshed automatically after 30 days.
- You can select up to 30 ad groups per rule.
Checking your custom audience status
You can view a custom audience’s status from the Audiences tab.
Status | Meaning |
---|---|
In progress | The system is currently building this custom audience based on its rule definitions. |
Available | The audience has finished building and at least 10,000 users have been mapped to the custom audience. |
Narrow | The audience was built successfully but only has between 0 and 10,000 members, which may negatively impact ad performance. |
Too narrow | The audience was built successfully but no users were able to be mapped to the audience. Consider broadening its rule definitions to include more OR terms. |
Failed | The system was unable to build this audience based on its rule definitions. |
Note
Custom audiences that are In progress or Failed can still be assigned to an ad group, but they won’t have any effect on ad delivery.