Skip to main content

6. How to Configure Buckets

The Configurations tab within each bucket lets you manage three key entities for tracking and routing leads:

  1. Sources – where your clients originate

  2. Postbacks – callback URLs for registration and first-trade events

  3. Snippets – embeddable code to drive new sign-ups

To add a new source:

The Sources list tags each lead with its origin (e.g. “Twitter,” “Facebook,” etc.).

  1. 1. Open your bucketbucket: 

    From Buckets, click the bucket name to drill in, then select Configurations.

  2. 2. Add a new sourcesource: 

    Click + New source next to List of sources.

  3. 3. Name the sourcesource: 

    Type the source name (e.g. Instagram) and press Enter (or click outside) to confirm.

  4. 4.Repeat: Repeat

    Add as many sources as needed by repeating steps 2–3.

  5. 5. Remove a sourcesource: 

    Hover over an existing source tag and click the ✕ to delete it.

You can view all sources for a specific bucket from the main Buckets page. To do that:

  1. Navigate to the Buckets tab.

  2. Click on the three-dot menu in the upper-right corner of the bucket.

  3. Select Show sources from the list.

    4. 4.

  4. A drawer with the list of sources (Twitter, Instagram, Facebook) will appear.

The Postbacks entity allows you or your partners to control and track user traffic and activity within our CRM system. Once a user registers in our CRM, a request is sent to the configured postback URL. Similarly, when the user completes their first transaction, a request is also sent to the configured postback URL.

You can add postback URLs for two types of activity:

    1. FTD (First Time Deposit)
    2. Registration
To add a new postback:

Postbacks let you notify external systems whenever a user registers or makes their very first transaction (FTD). You configure them per‑bucket on the Configurations tab:

  1. Open Your Bucket’s Configurations: In the left nav, click Buckets, select the bucket you want, then choose the Configurations tab at the top.

  2. Enable the Postbacks Panel: Flip the toggle at the top of the Postbacks card to “on” if it isn’t already.

  3. Enter the Callback URL: In the Postback URL field, type the full HTTPS endpoint your system will expose.

Use mustache placeholders ({{…}}) to inject dynamic client data. Only these tokens are allowed:

{{email}} → client’s email address {{status}} → “Registration” or “FTD” {{subID}} → the Sub ID you entered on the client profile {{affiliateID}} → the client’s Affiliate ID {{sourceID}} → the tracking source identifier

Hover the ℹ️ icon next to Fields to view the complete, supported placeholder list. Any other token (e.g. {{phone}}) will fail frontend validation (red warning) and be passed through as literal text if it somehow reaches the backend.

Select the Trigger Event: From the dropdown to the right of the URL, pick Registration (fires on every new signup) or FTD (fires once at first transaction).

Add the Postback: Click the green ➕ button to insert your URL+event into the active list.

Confirm & Save: You can immediately click away or hit the bucket’s Save button.

A “Success! Bucket configuration successfully updated” toast appears once your new postback is accepted.

Editing or Disabling

  • Edit any existing entry by clicking its ✏️ icon, updating the URL or event type, then saving.

  • Disable temporarily by flipping the entry’s toggle switch off—no removal needed.

The Snippet entity provides customizable code that you can insert into your website or social media page to attract clients to the platform. You can configure the code in various formats through Settings > Texts > Code Snippets.

To get a snippet:

Snippets are blocks you can embed on websites or ads to route new leads directly into this bucket.

Once highlighted, click Copy to grab the snippet text.

You can also get a snippet from the main Buckets page. To do that:

  1. Navigate to the Buckets tab.

  2. Click on the Show snippet icon near the specific bucket.

    3. 3.

  3. A drawer with the snippet will appear.

Tip: All changes take effect immediately for new leads. Existing leads retain their original source/postback assignments unless you manually update them. By carefully configuring your Sources, Postbacks, and Snippets, you ensure accurate lead attribution and seamless integration with external systems

Back to top