Targeting Rules
Targeting rules control who sees your placements.
You can show placements to new or returning users, users with something in their cart, or users in a certain location to just name a few of the options.
Targeting filters are broken into two categories; backend and frontend. Backend filters are items stored within Ampry while frontend filters are elements that Ampry can read once the page loads.
This creates an important distinction because it can affect how your placements load.
A main priority for Ampry is how quickly your site and the Ampry placements load. In order to increase loading times the Ampry software currently uses the following logic to select a placement:
Look at what page the visitor is on.
Choose 1 placement from each placement type targeted to that page.
Select a template to display.
Display the template.
If you select frontend filters the Ampry system will go through steps 1-3 before the site loads which could mean that a template is selected to fire that doesn't match the targeting settings of that template. In short, that template will never fire.
A workaround for this is to use the Weight feature.
Weights range from 1 to 10 with 10 being the highest. The higher the weight the more likely that placement will be selected.
You should select which template is most important to show and set its weight higher if you're using multiple templates in the same placement and segmenting the users based on frontend targeting rules. This will ensure that the most important template, say an exit intent unit for users that have something in their cart, is shown the most consistently.
Targeting rules are broken between backend and frontend settings as follows:
Backend Filters
- Platform (mobile/desktop)
- Language
- Subid
- URL
- Source
- Visited URL
- Geolocation
- New / Returning
- Subscribers
- Converted Events
- View Events
Frontend Filters
- Shopify
- JavaScript Function
- JavaScript Variable
- HTML Element
- Cookie