The short answer
A click identifier distinguishes an individual visit, while a SubID carries tracking information in a field accepted by the network. Start with your own campaign tracking link, replace example placeholders with the variables supported by your tracker, and verify the received values. An attractive destination page or a URL containing braces is not evidence that attribution has been configured correctly.

Separate the personal link from measurement fields
Your personal campaign link and its query parameters have different jobs. The link provides the assigned affiliate route; the parameters carry additional information for measurement. In Cash Nutra, use the personal tracking link supplied for the relevant affiliate and campaign. Do not rebuild its path from a campaign name, an identifier displayed in an administrative table, or a link that belongs to another partner.
Consider two ads promoting the same offer. They may share an affiliate route, but you still need to distinguish the visits they generate. A unique click reference supports individual matching, while an ad reference supports grouped comparisons. Reusing one fixed value for every click removes that distinction. Before adding fields, write down the questions your reports should answer and identify which values will make those answers possible.
Adapt the placeholders supplied in a Telegram message
A manual message may include this suffix: ?sub2={your_click_id}&source_id={affiliate_id}. This is an editable example, not a universal expression that every tracker understands. Replace {your_click_id} with your tracker's documented click variable. For {affiliate_id}, confirm the value or variable expected by your integration rather than assuming that any account identifier shown elsewhere is suitable.
Keep the personal path before the question mark unchanged. Do not append a slash to the opaque token or replace that token with something easier to read. When a link already contains parameters, update the relevant fields without adding a second question mark or conflicting copies. Save the template in the tool responsible for substituting its variables. Opening the unprocessed example directly from a messaging app does not exercise that substitution step.
Create a small parameter dictionary
Use four columns: information needed, outgoing field, value origin, and fictional test example. One row might describe the click identifier sent in sub2; another can describe the source reference sent in source_id. Keep examples recognisable without using actual customer records. Email addresses, phone numbers and order details are not convenient substitutes for test references and should not be placed in these fields merely to simplify a search.
Give every field a stable meaning. A column should not represent country in one report and creative identity in another unless the mapping change is explicitly versioned. More dimensions do not automatically produce better decisions. For an initial integration, a reliably matched click and a clear source reference are more valuable than a long collection of parameters that nobody on the team can explain or consistently interpret.
Check substitution at the responsible step
Make a controlled visit through the tracker using the test mechanism permitted for your integration. Then find the received value in the network information available to you, or ask your manager for a targeted check. A value still equal to {your_click_id} after the tracker should have replaced it indicates that substitution has not happened. Resolve that problem before investigating a conversion notification further down the flow.
However, a parameter missing from the final browser address is not proof that it was discarded. A redirect may record information without displaying it on the destination page. Look for evidence of receipt at the appropriate stage, using the test time and reference. Change one variable at a time. Reaching the expected page checks the visible destination; it does not independently establish that every tracking field arrived with its intended value.
Avoid encoding and copying mistakes
URL tools can encode characters and handle repeated parameter names. MDN explains these behaviours for URLSearchParams. Prefer your tracker's link builder when one is available, then inspect its output; manual concatenation can introduce unwanted separators or duplicate values.
In your test procedure, compare the expected value with the received value rather than judging only whether the whole link looks plausible. A copied space, punctuation attached to the end of a URL, or a variable substituted at the wrong stage can complicate diagnosis. Keep a private reference configuration. In a public support discussion, share field names and fictional examples, not the complete personal token. Supply the full link only through the appropriate private channel when it is necessary.
Connect the received click to a conversion test
After confirming receipt of the click value, check the conversion return with an authorised test. Establish which postback field should carry that identifier and which event should appear in the report. Do not create a real paid order or use customer details to manufacture technical evidence. The test record should follow one reference through the relevant stages while excluding information that the investigation does not need.
If the click exists but the return cannot be found, examine the expected event, report filters and return mapping separately. Replacing the personal campaign link is not a general remedy for every tracking issue. An incoming macro change should follow evidence about the incoming value; a postback change should follow evidence about the return. Keeping these decisions separate makes a successful correction explainable and makes later regressions easier to investigate.
Leave a configuration another operator can understand
Before handing the setup to a colleague, record the tracker, campaign, field meanings and test date. Store the relevant evidence where authorised team members can retrieve it. A new traffic source using different variable syntax deserves its own targeted check, even if the offer and personal campaign link remain unchanged. Record what changed rather than relying on a message saying that tracking worked at some point.
When preparing your Cash Nutra application, describe the markets and sources you intend to use and bring your tracking requirements to the manager. Once campaign access is confirmed, retrieve the personal link and clarify any uncertain mapping. This preparation does not promise conversions or profitability. It gives you a measurement process you can explain before making acquisition decisions from the numbers it produces.
Before you launch
- Keep the supplied personal link path unchanged.
- Replace example placeholders with documented tracker variables.
- Record the meaning and origin of every field you use.
- Verify a received value after an authorised test click.
- Check the conversion return separately from the visible destination.
Frequently asked questions
Should I keep {your_click_id} exactly as written?
Only if your tracker explicitly documents that variable. In the message it marks where your tracker's click variable belongs. Check that a real value replaces it during the intended flow.
Can source_id switch the link to another affiliate account?
Do not use it for that purpose. Start with the personal link assigned to your own account. A measurement parameter is not a substitute for the correct partner identity or campaign permission.
Must I post my full link when asking for help?
Use the appropriate private support channel when the full link is needed. For public explanations, provide fictional values and remove the personal token from the example.
Sources and references
- MDN: working with URL search parameters
Technical reference for encoding and repeated parameters, not a specification of Cash Nutra tracking macros or attribution rules.