Skip to main content

How to Create a Traffic Source

Rinku supports two types of traffic sources: custom and integrated. The type you choose affects how parameters are configured and what optimization features become available.

Custom vs Integrated Sources

CustomIntegrated
SetupManual parameter mappingAuto-filled from network template
Supported networksAnyAdsterra, ExoClick, Galaksion, HilltopAds, PropellerAds, RichAds, TrafficStars
Zone blockingManual onlyManual + automatic via API
Auto-optimizationAvailable if enabled on the campaign

Custom sources work with any traffic network. You define which parameters the source passes and configure everything manually.

Integrated sources are linked to a supported network account via API. The form pre-fills the correct parameter mapping for that network, and Rinku can block underperforming zones automatically through the network's API when optimization rules trigger.

To connect an integrated source, you first need to add the network account in Integrations. See the Optimization overview for more on what integration unlocks.


Step-by-step

1. Open the Sources tab

Go to the Sources tab and click New Source.

2. Choose the source type

  • To create a custom source, click Custom.
  • To create an integrated source, click the network name (e.g. ExoClick, Adsterra). The form will pre-fill parameter mappings and prompt you to select a connected network account.

3. Set the name

Enter a readable Name for this source (e.g. "Propeller Ads", "ExoClick Main", "AdNetwork X").

4. Configure input parameters

In the Input Parameters section, you define which parameters the source will pass to Rinku. For each parameter you'll see:

  • Label — a readable name
  • Placeholder — what to insert into your tracking links

For custom sources, the form shows the standard net_* fields and several tokens by default. For integrated sources, the correct mapping for that network is filled in automatically.

You can add or rename tokens — up to 30 tokens (token_1token_30) are available. Assign readable names in Account Settings.

Default mapping (custom sources):

Internal fieldDefault external name
net_external_idexternal_id
net_sourcesource_id
net_pidpid
net_creativecreative_id
net_campaigncampaign_id

You can change these names to match what your network actually sends.

5. (Optional) Connect an external account

For integrated sources, select an existing network account from the dropdown, or click Connect new account to add one inline. This connection is what enables automatic zone blocking.

6. (Optional) Configure Source Postback

If you want Rinku to send postbacks back to your traffic source:

  • Enter the Postback URL the source expects
  • Configure which fields to include and in what format

7. Save

Click Save. On the source detail page you'll see:

  • Source ID, name, campaign count
  • Input parameters and postback settings
  • Tokens to copy into your campaign tracking links

8. Use it in a campaign

When creating or editing a campaign, select this source in the Traffic Source field. Rinku will use the input parameters you configured when generating tracking links and processing incoming clicks.


Simple example

https://rinku.cc/c/ABCDEF?rinku_token={source_token}&sub1={token_1}&cid={click_id}

With network fields

https://landing.example.com/offer?pid={net_pid}&source={net_source}&ext_id={net_external_id}&cid={click_id}

Postback example

If your source postback URL template is:

https://partner.example.com/postback?cid={click_id}&payout={payout}&sub1={token_1}

Rinku will replace {click_id}, {payout}, and {token_1} with real values and fire the request on each conversion.


Common issues

ProblemSolution
Source not passing expected parametersCheck that the placeholders in the partner's link match the input parameters configured here
Source not visible when creating a campaignMake sure the source was created under the same account you're currently using
Network account dropdown is emptyGo to Integrations and connect an account for the selected network first

Next steps