Keitaro Integration Guide

To set up server-to-server (S2S) conversion tracking for the Blockchain-Ads network using Keitaro, you’ll configure Blockchain-Ads to generate a postback URL (where Keitaro will send conversion data) and then integrate it as a custom traffic source in Keitaro. This ensures Keitaro captures the {clickid} from incoming traffic and fires postbacks back to Blockchain-Ads with matching click IDs, revenue, and other details.

Step 1: Create the S2S Conversion Event in Blockchain-Ads

1. Log in to your Blockchain-Ads HUB dashboard.
2. Navigate to Advertising > Tracking > Create Conversion > Server to Server.
3. Follow the on-screen instructions to set up the event:
   
   • Name the conversion event (e.g., “Lead” or “Sale”).
   • Specify the event type (e.g., lead, purchase) and any revenue fields if applicable.
   • This will generate a unique tracker ID for your event and a postback URL in the format:

 GET https://server.blockchain-ads.com/www/delivery/tracker-mobile.php?clickid={clickid}&trackerid=YOUR_TRACKERID&transaction_value={transaction_value}

• {clickid}: Placeholder for the unique click ID (Blockchain-Ads will match this to the original click).
• trackerid: Your fixed event ID (do not change it).
• {transaction_value}: Optional placeholder for revenue/payout amount (omit if not tracking revenue).

Copy this full postback URL—you’ll need it in Keitaro.

4. Save the event. Note: When creating campaigns in Blockchain-Ads, set your destination URL to your Keitaro campaign URL (e.g., https://your-keitaro-domain.com/campaign123?clickid={clickid}). Blockchain-Ads will automatically append the real click ID value.

Step 2: Add Blockchain-Ads as a Custom Traffic Source in Keitaro

1. Log in to your Keitaro dashboard.
2. Go to Traffic Sources > Create.
3. In the “From template” field, search for “Blockchain-Ads”—if no template exists, select Custom or leave blank to build manually.
4. Fill in basic details:
   
   • Name: “Blockchain-Ads”.
   • Click ID parameter: Set this to clickid (this tells Keitaro to capture the incoming ?clickid=xxx value from Blockchain-Ads traffic and store it internally as the external ID for postbacks).
5. In the parameter template section (if prompted):
   
   • Add a row for the click ID:
     
     • Column 1 (Alias): Leave blank or set to “External ID” for reporting.
     • Column 2 (Parameter name): clickid.
     • Column 3 (Macro): Leave blank (since Blockchain-Ads appends the real value directly).
   • Add other parameters if needed (e.g., for campaign ID or subIDs from Blockchain-Ads macros).
6. In the S2S Postback field:
   
   • Paste the postback URL from Step 1.
   • Replace Blockchain-Ads placeholders with Keitaro equivalents:
     
     • {clickid} → {external_id} (passes the captured click ID back).
   • Example of a transformed URL:

https://server.blockchain-ads.com/www/delivery/tracker-mobile.php?clickid={external_id}&trackerid=YOUR_TRACKERID&transaction_value={revenue}

If you want to send only specific conversion statuses (e.g., approved leads), use the “Send only statuses” dropdown to select them (e.g., “Lead”, “Sale”).

7. Click Create to save the traffic source.
8. (Optional) If you have multiple campaigns, check Update in campaigns to apply this to existing ones.

Step 3: Set Up a Campaign in Keitaro and Test

1. Go to Campaigns > Create (or edit an existing one).
2. Select Blockchain-Ads as the Traffic Source.
3. Build your flow: Add streams, landing pages, and offers. For conversions:
   
   • If using affiliate offers, set up postbacks from the affiliate network to Keitaro (under Affiliate Networks).
   • Define conversion rules (e.g., S2S postback from offer, pixel firing, or custom events).
4. Generate and copy your Keitaro campaign URL (it will look like https://your-domain.com/abc?clickid={external_id}—paste this as the destination in your Blockchain-Ads campaign).
5. Test:
   
   • Launch a test campaign in Blockchain-Ads pointing to the Keitaro URL.
   • Simulate a click and conversion (e.g., via a test offer).
   • Check Keitaro reports (Reports > Conversions) for captured clicks/conversions.
   • Verify in Blockchain-Ads tracking that postbacks arrive (matching click IDs and revenue).
   • Use tools like Postman to manually fire a test postback if needed.

Tips and Troubleshooting

• Placeholders in Keitaro: Use {external_id} for clickid, {revenue} for amounts, and {status} for event types (e.g., map “lead” to a status). For unencoded values, prefix with _ (e.g., {_external_id}).
• Revenue/Currency: If conversions have varying currencies, use {revenue:USD} to convert.
• Errors: Ensure HTTPS for postbacks. If no data flows, check URL encoding, firewall blocks, or mismatched tracker ID. Keitaro logs postback attempts in Logs > Postbacks.
• Advanced: For multiple events, create separate conversion events in Blockchain-Ads and add multiple postback URLs in Keitaro (one per status).

This setup enables accurate attribution without cookies. For more Keitaro details, refer to their docs at docs.keitaro.io