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.

Conditions and Actions

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 URL contains a certain parameter.
  • The visitor is using a mobile device.
  • The visitor comes from a specific traffic source.
  • The visitor belongs to a selected audience segment.

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.


Common Condition Types

Condition Navigations

Depending on your Tango.ad configuration, available conditions may include:

URL Conditions

Display campaigns only on pages that match specific URLs or URL parameters.

Examples:

  • URL contains /checkout   
  • URL equals /pricing   
  • URL parameter utm_source=email   

URL-based targeting can be combined with other workflow rules in Conditions and Actions.


Visitor Conditions

Target campaigns based on visitor information.

Examples include:

  • New visitors
  • Returning visitors
  • Logged-in users
  • Customer segments

You can also use Meta Fields to work with custom visitor data and create more personalized targeting rules.


Device Conditions

Show different campaigns depending on the visitor's device.

Examples:

  • Desktop
  • Mobile
  • Tablet

Traffic Source Conditions

Display campaigns only to visitors arriving from selected marketing channels.

Examples:

  • Google Ads
  • Facebook
  • Email campaigns
  • Organic search

Custom Conditions

Use custom events, variables, or developer-defined values to create advanced targeting rules.

For advanced visitor data and event-based targeting, see Meta Fields and Trait Analytics API.


Actions

Actions Navigation

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 Campaign Settings to review campaign-level configuration before publishing.
  • Use Analytics Overview to evaluate campaign behavior and results after launch.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.