Skip to main content
Sequence nodes help you organize complex page event flows by ensuring actions execute in the correct order. Think of them as “for each” loops that process connected nodes one by one.

Understanding Sequence Nodes

A sequence node acts as an organizational container that executes all connected nodes in a specific order before proceeding to the next step in your flow.

How Sequences Work

  • Sequential execution - Processes each connected node completely before moving to the next
  • Top to bottom - Executes nodes from top to bottom when multiple nodes are connected
  • Completion control - Waits for all nodes to complete before continuing the flow
  • Flow organization - Helps structure complex logic into manageable chunks

Why Use Sequences?

  • Ensure execution order - Critical when some actions depend on others
  • Organize complex flows - Group related actions together
  • Improve debugging - Easier to track where issues occur
  • Better visual organization - Makes page event flows cleaner and more readable

Basic Sequence Usage

Creating a Sequence

  1. Go to Page Events for your page
  2. Click “Add Node”
  3. Select “Sequence”
  4. Connect the nodes you want to execute in sequence
  5. Connect the sequence to your main flow

Simple Example

Without Sequence (execution order not guaranteed):
With Sequence (guaranteed order):

Advanced Sequence Patterns

Multi-Step Whitelisting

Ensure visitors are properly whitelisted before showing content: Flow:
  1. Query Parameter Condition (vtID is not empty)
  2. Sequence contains:
    • Whitelist Visitor
    • Log Visitor Data
    • Split Test Component
  3. Continue to next flow step

Conditional Actions

Perform multiple actions based on a single condition: Flow:
  1. Script Rule (check affiliate ID = 100)
  2. Sequence contains:
    • Dynamic Container (show special pricing)
    • Log Affiliate Visit
    • Set Custom Tracking
  3. Continue to purchase flow

Data Processing

Process visitor data in a specific order: Flow:
  1. Page Load
  2. Sequence contains:
    • Capture Visitor Info
    • Validate Data
    • Store in Database
    • Send to Analytics
  3. Continue to page display

Best Practices

When to Use Sequences

  • Multiple dependent actions - When action B depends on action A completing
  • Data processing - When you need to process information in steps
  • Complex conditions - When you have multiple actions after a condition
  • Clean organization - When your flow is getting complex and hard to follow

When NOT to Use Sequences

  • Single actions - Don’t use sequences for just one node
  • Independent actions - When actions don’t depend on each other
  • Simple flows - When your flow is already clear and simple
  • Performance critical - When you need maximum speed (sequences add slight overhead)

Organization Tips

  • Group related actions - Put logically related nodes in the same sequence
  • Use descriptive names - Name your sequences clearly (e.g., “Affiliate Processing”)
  • Keep sequences focused - Don’t put too many unrelated actions in one sequence
  • Document complex flows - Add comments explaining what each sequence does

Integration with Other Features

Whitelisting Workflows

Sequences are perfect for complex whitelisting scenarios: Example: Affiliate-specific whitelisting

Split Testing

Use sequences to set up conditions before split testing: Example: Conditional split testing

Dynamic Content

Prepare data before showing dynamic content: Example: Personalized content

Common Sequence Patterns

Authentication Flow

Affiliate Processing

Purchase Preparation

Error Handling

Troubleshooting

Common Issues

  • Sequence not executing - Check that nodes are properly connected to the sequence
  • Wrong execution order - Verify the vertical order of nodes connected to the sequence
  • Sequence hanging - Check if any connected nodes are causing infinite loops
  • Performance issues - Consider if you have too many nodes in a single sequence

Debugging Sequences

  1. Test individual nodes - Make sure each node in the sequence works independently
  2. Check execution order - Verify nodes execute in the expected order
  3. Monitor completion - Ensure all nodes complete before the sequence continues
  4. Use browser tools - Check console for any JavaScript errors
  5. Test with different data - Verify the sequence works with various inputs

Performance Considerations

  • Minimize unnecessary sequences - Don’t use sequences unless needed
  • Optimize node order - Put faster nodes first when possible
  • Avoid blocking operations - Don’t put long-running operations in sequences
  • Consider parallel execution - Some actions might be better executed in parallel

Advanced Usage

Nested Sequences

You can connect sequences to other sequences for complex workflows:

Conditional Sequences

Use different sequences based on conditions:

Loop-like Behavior

While not true loops, sequences can simulate iterative processing:

Real-World Examples

E-commerce Flow

Lead Generation

Content Personalization

Use sequences where execution order matters or where grouping related actions makes the flow easier to read. Too many sequences can make a flow harder to debug.