Skip to main content

Dummy Postback: Setup and Configuration Guide

Introduction

The Dummy Postback feature allows you to configure automated postbacks to publishers after a specified number of clicks. This can be useful when you need to trigger an additional postback based on click volume for selected campaigns and publishers.

You can define the click threshold, select the applicable campaigns and publishers, add a conversion note, and control the rule's status.

Benefits of Dummy Postback

  • Automated postbacks: Automatically trigger postbacks once the defined click threshold is reached.

  • Flexible targeting: Apply the rule to specific campaigns and publishers.

  • Click-based triggering: Set a specific number of clicks required before the postback is triggered.

  • Better control: Enable or disable individual rules using the status option.

  • Easy customization: Add a conversion note and select the required goal based on your campaign requirements.

  • Manual exclusions: Publishers and campaigns can be manually excluded from the rule when required.

How to Set Up a Dummy Postback

Follow the steps below to create a dummy postback rule:

Step 1: Log in to the Trackier Panel

Log in to your Trackier account using your credentials.

Step 2: Navigate to Workflow Automation

From the panel, go to Automation and then select Workflow Automation.

Step 3: Select Dummy Postback

In Workflow Automation, locate and select Dummy Postback.

Step 4: Add a New Rule

Click on Action and select Add New Rule.

Step 5: Configure the Rule

In the Add Rule window, configure the following fields:

  • Campaigns: Select the campaigns to which the rule should apply.

  • Publishers: Select the publishers who should receive the postback.

  • Clicks (Excluding Rejected Clicks) >=: Enter the minimum number of clicks required to trigger the postback. For example, entering 100000 means the rule will trigger after 100,000 eligible clicks.

  • Conversion Note: Enter the note that should be associated with the postback.

  • Goal: Select the applicable conversion goal, such as Default.

  • Status: Set the rule to Active to enable it.

Note: The rule will trigger postbacks to publishers after the configured number of clicks. It will be applied to the selected publishers and campaigns.

Step 6: Save the Rule

Once all the required details have been configured, click Save to create the Dummy Postback rule.

Advantages of Using Dummy Postback

Advantage

Description

1

Automated postbacks

Postbacks are triggered automatically once the defined click threshold is reached, removing the need for manual tracking.

2

Flexible targeting

Rules can be applied to specific campaigns and publishers, allowing different logic for different partners.

3

Click-based triggering

You set the exact number of eligible clicks (excluding rejected clicks) required before the postback fires.

4

Better control

The Active/Inactive status lets you enable, pause, or disable individual rules at any time, and specific publishers or campaigns can be manually excluded.

5

Easy customization

You can add a conversion note and select the required goal to match your campaign requirements and simplify reporting.

Notes

  • The click count is calculated excluding rejected clicks.

  • The rule applies only to the campaigns and publishers selected during configuration.

  • Publishers and campaigns can also be manually excluded from the rule.

  • Make sure the rule status is set to Active if you want the postback to be triggered.

Conclusion

The Dummy Postback feature gives you a simple, rule-based way to send automated postbacks to publishers once a campaign reaches a defined click volume. By setting the click threshold, selecting the relevant campaigns and publishers, adding a conversion note, and choosing the goal, you can manage click-based postbacks without any manual monitoring. Because each rule has its own status, you stay in full control and can activate or deactivate it whenever your requirements change.

Setting up a rule takes only a few steps in Workflow Automation, and once it is saved, the system handles the rest.

Did this answer your question?