Preset groups — domains, IP ranges, app packages
Build a reusable domain, IP-range or app-package list once in the admin area and target the whole list with one Preset Domains, Preset IP Ranges or Preset App Packages rule — with the upload, deduplication, ten-minute propagation and "Clear does not propagate" behaviour you need to know before relying on it.
When a rule needs hundreds of values — a domain blocklist, a data-centre IP list, an app allowlist — adding them one at a time is impractical. A preset group is a named list an administrator maintains once in the admin area; any advertiser, campaign, banner, site, zone or placement then targets the whole list with a single Preset Domains, Preset IP Ranges or Preset App Packages rule. A rule stores only a reference to the group, so editing the list changes what every rule that points at it does — on the ad servers’ ten-minute reload cycle.
Example. The administrator uploads a 1,200-line gambling-domains.txt into a group titled
Gambling domains. The network manager adds one Preset Domains → Exclude rule on the
advertiser Lakeshore Finance; all of its campaigns stop serving on those 1,200 domains and
every subdomain of them. When 30 more domains are uploaded next week, every rule pointing at the
group follows within ten minutes — no campaign is touched.
Typical scenarios
| You want | Set | Where |
|---|---|---|
| A brand-safety domain blocklist shared by every advertiser | Group Gambling domains (upload a .txt); Preset Domains → Exclude on each advertiser | Admin → Targeting presets; advertiser → Targeting |
| Keep data-centre traffic off a placement | Group Data-centre IPs with from–to ranges (not CIDR); Preset IP Ranges → Exclude on the placement | Admin → Targeting presets; placement → Pre-targeting |
| A campaign that serves only in 60 approved apps | Group Approved apps with the bundle IDs; Preset App Packages → Include on the campaign | Admin → Targeting presets; campaign → Targeting |
| Two allowlists on one campaign | One rule per group — two Include rules of the same dimension are OR-ed | Campaign → Targeting |
| The same list on a second network | Export the group on the list page, Import the CSV on the other network | Admin → Targeting presets → list page |
Step by step
Create and fill a group (administrator)
-
Go to Admin → Targeting presets → Preset domain group management (or the Preset IP ranges / Preset application package variant — all three pages behave identically apart from the entry shape).
-
Create the group: press Add above the grid, enter a Title, then Save. A Done toast appears and the page reloads with the group’s id in the URL, which is what makes the entries grid below appear. The title is all account users see in the targeting picker — never the entries — so name it for what it is: “Data-centre IPs”, “Gambling domains”.

-
Add entries one at a time: type the value in the field next to Add and press Add (Enter submits too). IP-range groups have a From and a To field instead of one value.

-
Or import in bulk — a two-step control, not a single button: click the Click to upload dropzone (or drag the file onto it; the dialog filters to
.txtand.csv, and the dropzone then shows the file name and an ✕ to unpick it), then press Upload. An Uploaded N record(s) toast reports how many rows were actually written — Uploaded N record(s), skipped M duplicate(s) when some were already there; any lines that failed validation come back in a second toast asInvalid resource <value>. The file is one value per line; lines are read as CSV with a comma delimiter and only the first column is used, soexample.com,notes,2026importsexample.com. -
Manage what is there: Search filters the grid server-side as you type (domain and app-package groups only); tick rows and press Delete (it asks Delete N record(s)?); Clear empties the whole group after Remove all entries?. Entries cannot be edited in place — correct a value by deleting it and adding it again.
Use a group in targeting (account user)
-
Open the entity’s Targeting card (or Pre-targeting on site, zone and placement) and make sure its switch is on. In the targeting type list — above the editor on a laptop screen, to its left on a wider one — under the Presets heading, choose Preset Domains, Preset IP Ranges or Preset App Packages.
-
Pick a group from the dropdown. It is a searchable single-select: one rule references exactly one group, and Include and Exclude stay disabled until you pick one.

-
Click Include or Exclude. The saved rule appears as a chip labelled with the group’s title. To reference several groups, add one rule per group — multiple Include rules of the same dimension are OR-ed at serve time.
Move a whole group to another network
- On the list page select one group row and press Export — the server sends that group’s entries as a CSV named after the group. On the destination network press Import and pick the file. The import always creates a new group, titled after the file name with its extension dropped; it never merges into a group that is already there, and it refuses a file whose name matches an existing group (“A group named X already exists”) — rename the file to bring in a second copy. A file that cannot be read is reported on the file field, and nothing is created.
Caveats and exceptions
Propagation
- Changes take up to ten minutes to affect delivery. The ad servers pick up changed preset groups every 10 minutes by default. Add a domain and check the log a minute later and you will see the old behaviour — that is the refresh delay, not a lost save.
- To stop a preset rule, delete the rule, not the group’s contents. Emptying a group with Clear does not stop the ad servers enforcing the entries it held. To stop a preset rule taking effect, delete the rule on the entity.
- An empty group never matches anything — including a brand-new group you have not filled yet. An Include rule on an empty group therefore blocks all delivery for that entity on that dimension, while an Exclude rule on one quietly excludes nothing. Fill the group before you point rules at it.
- Deleting a group in use also removes its rules. When targeting rules still use the group, Delete first asks for confirmation and lists the entities they belong to (Banner #12 “Summer sale”, Campaign #3 “Q3 retargeting”). Confirming deletes the group and every targeting rule that points at it, so those entities stop being restricted — or stop being excluded — on that dimension straight away. Cancel leaves everything as it was. To keep an entity restricted, point its rule at another group before you delete this one.
Uploads and duplicates
- Uploads append. There is no “replace the list” upload — to swap a list out, Clear first (accepting the propagation problem above) or delete the group and build a new one.
- Duplicates are skipped, not added twice. Values already in the group, and repeats within the file, are both skipped: the entries are collected into a set before they are written, so Uploaded N counts only what was actually added. Values the group already held are reported as skipped M duplicate(s); repeats within the file are folded before that count, so they show up only as a total lower than your file’s line count. Re-uploading the same file is therefore safe, and a file of 500 domains landing on an existing group can legitimately report Uploaded 3 record(s), skipped 497 duplicate(s).
- Deduplication ignores case. A group cannot hold two values that differ only in case:
Example.comis skipped when the group already holdsexample.com, and when a file contains both spellings only the first one is saved. The stored spelling is whichever arrived first. - Invalid lines never abort an upload. The valid remainder is saved and each bad line comes
back as
Invalid resource <value>in a separate toast. Read that toast on a large import — it is the only place the rejections are shown. - Adding a value manually that the group already holds reports Done and adds nothing — no duplicate row, and no message telling you it was already there. Search for the value first if you need to know.
- Export stays disabled until exactly one group row is selected — it exports the entries of the selected group, not the list of groups.
Who can do this
- Maintaining groups — administrators only. Each of the three admin pages is gated by an admin-area permission of the same name, assigned per admin role in Admin → Users & access → Admin roles & permissions; without it the page is missing from the nav and returns HTTP 403. Account users never reach the admin area.
- Using groups in targeting — an account user picks a group from the preset dimension of a Targeting or Pre-targeting card. Most of those dimensions are off for the default account roles: an advertiser has Preset IP Ranges and Preset App Packages but not Preset Domains; a network manager has none on either side as shipped; a publisher has no Pre-targeting card, so no preset dimension on the supply side. A dimension your role cannot use is simply not listed — there is no greyed-out entry; once it is listed, its picker shows every group of that kind, so an empty picker means no group exists yet. On a Can View share saved preset rules are read-only.
- Nothing stops two groups sharing a title, and the targeting picker shows only titles. Two groups called “Blocklist” are indistinguishable to the account user choosing one.
Not working?
| Symptom | Check | Where |
|---|---|---|
| A domain you just added is not blocked yet | The ad servers reload preset groups every 10 minutes. | Wait; check the log again later |
| You cleared the group but the entries still apply | Clear does not propagate. Delete the rule on the entity instead. | Entity → Targeting → the preset chip’s ✕ |
| An Include rule stopped all delivery | The group is empty (or the picker named a different, empty group with the same title). | Admin → Targeting presets → the group’s grid |
| Uploaded 3 record(s), skipped 497 duplicate(s) | Expected: the group already held the rest. Repeats within the file do not show in the count at all. | — |
| Some lines were refused | A second toast lists each Invalid resource <value>: a domain over 128 characters, a CIDR range (10.0.0.0/24 — write a from–to pair), a package with a hyphen or space, a line with more or fewer than one hyphen in an IP-range file. | The second toast; the table below |
| Preset Domains is missing from the type list | Your role lacks that dimension; it is not greyed, it is absent. | Your administrator (role grants) |
| The picker is empty | No group of that kind exists yet. | Admin → Targeting presets |
| Export is disabled | Select exactly one group row first. | The list page |
| Import refuses the file | ”A group named X already exists” — rename the file; or the file cannot be read (reported on the file field). | The list page |
| A rule vanished from an entity | Its group was deleted; the confirmation listed the entities. | Admin → Targeting presets |
| A 403 from the preset API | The domain and IP-range endpoints need Preset Domains Group, the app-package endpoints Preset App Packages Group — separate from the three admin-page permissions. | API client permissions |
Reference
The three group kinds
| Group kind | Admin page | Entry shape | A valid entry is… |
|---|---|---|---|
| Preset domains | Preset domain group management | One domain per line (news.example.com) | A syntactically valid domain name, or a public suffix from the Mozilla Public Suffix List (so com and co.uk are accepted as whole-TLD entries). At most 128 characters — a longer value is rejected as invalid. |
| Preset IP ranges | Preset IP ranges group management | from-to per line (10.0.0.1-10.0.0.255); the manual form has separate From and To fields | Two addresses separated by a hyphen, both valid, from ≤ to. IPv4 and IPv6 both work. CIDR is not accepted — 10.0.0.0/24 fails, write it as a from–to pair. A line with anything other than exactly one hyphen is rejected. |
| Preset app packages | Preset application package group management | One bundle id per line (com.example.app) | A dotted Java-identifier-style name: each dot-separated segment must start with a letter, _ or $ and contain only letters, digits, _ or $. Hyphens and spaces are rejected. At most 128 characters — a longer value is rejected as invalid. |
Entries toolbar
| Control | What it does | Notes |
|---|---|---|
| Search | Server-side “contains” filter on the entry value | Domain and app-package groups only; the IP-ranges grid has none |
| Value field / From + To | The value to add manually | One field for domains and packages, a pair for IP ranges |
| Add | Adds one entry | Disabled until the field(s) are filled; Enter submits |
| Click to upload | Picks a file for bulk import — click or drag & drop | Only stages the file; nothing is imported yet |
| Upload | Imports the staged file | Disabled until a file is staged. Appends — never replaces |
| Delete | Removes the ticked rows | Disabled with nothing selected; confirms first |
| Clear | Removes every entry in the group | Disabled on an empty group; confirms first. Does not reach ad serving — see Caveats |
| Refresh / pager | Re-reads the grid; pages through entries | Default page size 25 |
What an entry matches at serve time
| Kind | Compared against | Matching rule |
|---|---|---|
| Preset domains | The request’s referrer domain, taken in turn from the rd parameter, the Referer header, the request-URL parameter, the request URL itself and the Origin parameter | Case-insensitive, and matches on label suffixes: an entry example.com also matches news.example.com and a.b.example.com. An entry that is a bare TLD (com) therefore matches every .com domain |
| Preset IP ranges | The client IP address | Inclusive of both bounds; overlapping ranges in one group are merged; IPv4 and IPv6 |
| Preset app packages | The app bundle id on the request | Case-insensitive, and matches on dotted prefixes: an entry com.example also matches com.example.app and com.example.app.free |
Permissions
| Permission | Lets you |
|---|---|
| Admin-area page permission of the same name (per admin role) | Open the group management page |
| Preset Domains / Preset IP Ranges / Preset App Packages targeting (or pre-targeting) dimension | See the dimension in the card and add rules |
| Preset Domains Group / Preset App Packages Group | Call the REST endpoints (domains and IP ranges; app packages) |
Over the API
Group CRUD, entry add and delete, and the file uploads exist for all three kinds under
/rest-api/preset-domain/…, /rest-api/preset-app-package/… and /rest-api/preset-ip-ranges/… —
the verbs, parameters and curl examples are in
Targeting, capping and limits over the API. The
domain and IP-range endpoints check the Preset Domains Group permission, and the app-package
endpoints check Preset App Packages Group. Neither is one of the three admin-area page
permissions above, so an API client needs them granted separately.