Conditions and Actions

Conditions control who sees your campaign by evaluating specific rules before the workflow continues. Actions control what happens when a visitor meets a condition or interacts with your campaign.
For an overview of how workflows are structured, see Workflow Editor Overview.
What are Conditions?
Conditions act as decision points within a workflow. They evaluate visitor data, page information, or other criteria to determine what should happen next.
For example, you can show a campaign only if:
- The visitor is on a specific page.
- The visitor is using a mobile device.
- The visitor comes from a specific traffic source.
- The visitor has a specific shopping interest.
- The visitor meets specific visitor profile criteria.
For more information about starting workflows, see Triggers.
How Conditions Work
Trigger
↓
Condition is evaluated
↓
Match?
┌───────────────┐
│ Yes │
│ Continue to │
│ next step │
└───────────────┘
│
▼
Campaign displays
No
│
▼
Otherwise branch
or End Campaign

Conditions are configured as part of the workflow logic. See Building Workflows for guidance on creating multi-step workflows.
Condition Categories
The Workflow Editor includes the following condition categories:
Visitor Behavior
Use visitor behavior data to determine which visitors should continue through the workflow.
Traffic Source
Use the visitor's traffic source to determine which workflow path they should follow.
Shopping Interest
Use shopping interest data to create targeted workflow conditions.
Cart
Use cart-related information when defining workflow conditions.
Datalake
Use available Datalake data as part of your workflow conditions.
Campaign History
Use a visitor's campaign history when determining which workflow path they should follow.
Session
Use session-related information to define workflow conditions.
Visitor Profile
Use visitor profile information when determining which visitors should continue through the workflow.
For more information about workflow conditions, see Workflow Editor Overview.
Actions
Actions define what happens after a visitor interacts with your campaign or when a workflow reaches a specific point.
Actions allow you to build dynamic customer journeys by responding to visitor behavior.
For a complete overview of workflow behavior, see Workflow Editor Overview.
What are Actions?
An action is performed automatically when an event occurs.
For example, when a visitor clicks a button, copies a coupon code, or closes a popup, Tango.ad can immediately perform one or more actions.
Common Actions
Depending on your workflow, actions may include:
Display Popup
Show a popup to the visitor.
Used to:
- Display promotional offers
- Show newsletter sign-up forms
- Present product recommendations
See Working with Components for information about designing campaign content.
Show Sticker
Display a sticker on the page.
This is commonly used after a popup is dismissed so visitors can reopen the campaign later.
Go to Another Step
Move the visitor to another workflow step.
This enables:
- Multi-step popups
- Surveys
- Guided customer journeys
- Progressive offers
For more information, see Building Workflows.
Finish Campaign
End the workflow for the current visitor.
No additional campaign steps are shown.
Log Event
Record a visitor action for analytics and reporting.
Examples include:
- Popup viewed
- Button clicked
- Coupon copied
- Form submitted
Logged events can contribute to analytics and visitor insights. See Analytics Overview.
Call Script
Execute a custom JavaScript function or integration.
This action is typically used for advanced workflows and third-party integrations.
For developers working with visitor and ecommerce data, see Ecommerce API.
How Actions Work
Visitor interacts with campaign
↓
Event occurs
↓
Action is triggered
↓
Workflow continues
A single event can trigger one or multiple actions depending on how the workflow is configured.
Example Workflow
Page Load
↓
Condition:
URL contains "/sale"
↓
Display Popup
↓
Visitor clicks "Get Coupon"
↓
Copy Coupon Code
↓
Go to Step 2
↓
Show Thank You Message
↓
Finish Campaign
You can combine triggers, conditions, and actions to create complete customer journeys. See Build Multi-Step Customer Journeys for a practical use case.
Best Practices
- Keep conditions as simple as possible to make workflows easier to maintain.
- Use conditions to target the right audience instead of creating multiple similar campaigns.
- Organize workflows with clear branching for different visitor scenarios.
- Use actions to guide visitors naturally through multi-step experiences.
- Test every condition and action before publishing to ensure the workflow behaves as expected.
- Use Analytics Overview to evaluate campaign behavior and results after launch.