Advanced Targeting
Target animations to specific pages using post types, custom URLs, and RegEx patterns.
By default, a timeline is assigned to a single page. Advanced Targeting lets you load it on multiple pages at once — by post type, specific URL patterns, or custom RegEx rules — without duplicating the timeline.
Location
Left Panel → Settings tab → Advanced Targeting
Open the Settings tab for any timeline. The Advanced Targeting section sits below the Global toggle and the single-page selector.

Default Behavior
Every timeline starts with a single target:
| Setting | What It Does |
|---|---|
| Page selector | Assigns the timeline to one specific page (tSelectPost). The baseline — pick the page where the animation lives. |
| Global toggle | When enabled, the timeline loads on every page of the site (tGlobal). Overrides the page selector and Advanced Targeting. |
| Advanced Targeting | Sits between these two extremes — target a specific group of pages without going fully global. |
Use Advanced Targeting when the same animation should appear across a category of pages (all blog posts, all product pages) or on any URL that matches a pattern.
Post Type Targeting
Select one or more post types and the timeline loads on every page that belongs to those types — Pages, Posts, Products, or any custom post type registered on your site.
How to use it:
- Open Left Panel → Settings tab → Advanced Targeting.
- Click a post type chip to toggle it on. Selected types are highlighted.
- The timeline will now load on all pages of that type, in addition to the single page set in the page selector.
This is the fastest way to apply a consistent animation across your entire blog, all WooCommerce products, or any uniform content type.
Custom RegEx Targeting
For URL-based rules, the RegEx input matches the timeline against any page whose URL fits the pattern.
How it works:
- Type a valid RegEx string directly — no delimiters needed. Delimiters are inserted automatically.
- The only supported flag is
i(case-insensitive match). Other flags are not available. - Special characters (
.,?,+,(,), etc.) must be escaped with a backslash. - The pattern is matched against the URL path, not the full URL (no protocol or domain).
Pattern Examples
| Pattern | Matches | Description |
|---|---|---|
/about/ | /about/, /about/team/ | Any URL containing /about/ |
^/blog/ | /blog/post-1, /blog/ | URLs starting with /blog/ |
\.html$ | /page.html | URLs ending in .html |
/products/[0-9]+ | /products/123, /products/456 | Product pages with numeric IDs |
^/en/ | /en/home, /en/contact | All pages under a language prefix |
Tips & Gotchas
- Pattern scope — RegEx matches the URL path only, not the full address.
/about/targets paths that contain/about/, nothttps://example.com/about/. - Broad patterns are risky — A loose pattern like
/pagewill match/page-one,/page-two,/contact-page, and anything else containing “page”. Narrow your patterns when possible. - Skip
.*for global — If you want an animation on every page, use the Global toggle instead of writing a catch-all regex. It’s more explicit and has no edge-case risk. - Case sensitivity — The
iflag makes the match case-insensitive. Without it (by default),/About/would not match/about/. Enable it by appendingiafter the pattern if your site uses mixed-case URLs. - Combine with Breakpoints — Advanced Targeting controls which pages load the animation. Breakpoints control at which viewport widths it runs. Use both together for precise delivery.
Related
- Advanced Targeting in the SDK — Apply post type and URL targeting directly in code
- Breakpoints — Enable or disable animations at specific viewport widths
- Overview — Builder fundamentals and how timelines are structured