A Flow answers one question: “If this visitor fits these conditions, where should they go?” TapBaton checks Flows from top to bottom. The first match wins.
Start with the Default Flow
Section titled “Start with the Default Flow”Give the Default Flow a destination before adding audience rules. It handles visitors who do not match a Flow above it. This is also useful when the source app or another signal cannot be identified.
Add a specific audience
Section titled “Add a specific audience”- Select Add flow.
- Name it for the audience, such as “Instagram on iPhone”.
- Under Specific audience, add a filter. Choose the type of signal, how to match it, and the value.
- Choose the destination.
- Use Test route with a matching and a nonmatching example.
All filters on one Flow must match. If a required signal is unknown, TapBaton continues to the next Flow. Move a more specific Flow above a broader one so it gets checked first.
Choose a destination
Section titled “Choose a destination”The editor offers Open a website, Open an app, and Custom sequence. Choose the action that matches what your visitor should open. For a website, enter its full address. A visitor who opens it from an in-app browser is taken to their own browser automatically; whether that works depends on the device and app, so test it with a real visit before using it widely.
If a Flow has more than one destination, assign weights to split its traffic. Equal weights split traffic evenly; a 3-to-1 split sends about three quarters to the first destination over many visits. Individual small samples can vary.
Keep a visitor on one destination
Section titled “Keep a visitor on one destination”Every Smart Link has one setting for this, Uniqueness period, below the flows. It runs from 1 to 8640 hours, and new links start at 24. Inside that period, a repeat click from the same visitor on the same Smart Link is not counted as a unique click, and the visitor always reaches the same destination when a Flow has more than one. There is no separate switch: every Flow with several destinations works this way.
TapBaton recognizes a visitor from their network address and browser details, without a cookie, so the match is approximate. People who share a network and browser can look like one visitor, and one person on two devices looks like two.
Periods run on fixed UTC times, not from each visitor’s first click. A 24-hour period ends at midnight UTC. A visitor whose clicks fall on either side of the end of a period counts as a new visitor and may be sent to a different destination. A longer period connects one person’s visits for longer, so choose the shortest period that fits your campaign. After you change the period and publish, every visitor starts a new period.
Prepare for an unavailable route
Section titled “Prepare for an unavailable route”You can set a shared Fallback URL and choose what happens When no flow matches. These cover different situations: a fallback offers another place to go if the chosen route cannot be used; no-match behavior decides what to do when no Flow applies.
Keep both destinations useful to a real visitor. Preview the draft, then make a real test visit before publishing to a campaign.
Pass campaign details along
Section titled “Pass campaign details along”You can forward incoming link parameters to a destination. This helps a landing page or tracking partner see which campaign sent the visit. If you use placeholders in a destination address, check the preview with a sample value and confirm the receiving page or partner expects it. Learn about tracking results.