E-commerce
September 3, 2026
Are you wondering how to respond to a partner who disputes a commission, claiming an unrecognized UTM link or incorrect attribution? Attribution should never be left to impression, but must be based on clear and verifiable technical rules.
Conflicts often arise when the partner's perceived value of the generated traffic collides with technological constraints such as cookie duration or channel prioritization. The role of support is not to promise a systematic correction, but to provide factual evidence and explain the invisible mechanisms of tracking.
So how do you structure this response without fueling the controversy? On the agenda:
Why is attribution a friction zone for merchants?
What technical data must be checked before responding?
How do you explain a non-attribution in a factual way?
How should evidence be managed in borderline cases?
What rules need to be clarified to avoid recurring conflicts?
Let's get started.
Summary
Why is attribution a point of friction for merchants?
The Invisible Complexity of Tracking
Attribution often determines who receives the commission for a sale. This is a sensitive topic because it directly conditions the revenue of your affiliate partners or ambassadors. When a partner believes they generated the interest, but the system does not grant them the commission, resentment quickly sets in.
The problem often stems from a mismatch between actual influence and the attribution validated by the tools. The customer may have seen the partner's link, clicked on it, but returned two days later to purchase through another channel or on a different device. Technology does not always capture this complete journey.
A disputed attribution must be handled with a clear rule, not with an impression of goodwill. The merchant must distinguish the partner's probable influence from an attribution technically validated by the site logs. Without this distinction, every claim becomes an emotional debate rather than a technical adjustment.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What technical data should be checked before responding?
The support's meticulous investigation
Before formulating a response, it is imperative to retrieve a precise set of information to verify the situation. Start by examining the UTM link provided by the partner and its accompanying parameters.
Next, check whether the partner's tracking code was correctly inserted or applied at the time of the order. The date of the interaction is crucial to know if the request falls within the attribution window allowed by your program.
It is also necessary to analyze the source of the last interaction before the purchase, the channel used, and the end device. The attribution model plays a central role: do you favor the last click, the first source, or a weighted combination? In parallel, check the status of the order to confirm if there was a return, cancellation, or payment failure that would automatically exclude the commission.
How can a non-attribution be explained in a factual manner?
Communicating Technical Barriers Without Guilt
Explaining why a sale is not attributed requires precision. If the UTM link was ignored or if the attribution window has expired, this is a technical fact that you must communicate clearly.
It often happens that another channel takes priority over your attribution model, such as a direct ad or a marketing email sent just before the purchase. If the order was cancelled or is being returned, your program's rules may exclude the commission for that specific transaction.
The response must remain strictly factual and explain the exact criterion blocking the attribution. Avoid saying "it's the system that decides," but rather "according to the 24-hour expired cookie rule." The partner must understand the technical criterion that applies to their specific case, without it seeming arbitrary.
How should edge cases be handled in terms of evidence management?
The burden of proof and the controlled exception
A screenshot of a conversation between the client and the partner or a shared link can help to understand the context. However, these elements never replace the program's attribution rule.
If a manual correction is possible, it must be validated by a manager and strictly tracked in your management system to ensure auditability. Exceptions must remain controlled so as not to open the door to systematic requests for bonuses or retroactive corrections.
In the event that multiple partners claim the same order, the response must explain the priority model provided in your charter. Without a clear rule on who is entitled to the commission in the event of an overlap, each dispute can become an isolated negotiation that undermines the credibility of your program.
What rules need to be clarified to avoid conflicts?
Transparency as a Preventive Tool
The program rules must be explicit about the attribution window, the priority model, and the types of excluded sales. Customer returns, cancellations, or the use of special promotional codes are often exclusion points that need to be clarified from the start.
Partners must be able to track their performance in real-time without having to wait for support for every detail. Support must escalate internally the rules that generate the most disputes so they can be revised if necessary.
Transparency drastically reduces useless debates. Furthermore, it is necessary to specify whether attribution is calculated at the initial click, at the confirmed order, or after validation of payment and the return period. This step significantly changes the moment when a commission becomes final for the partner.
Which workflow should be followed to process a complaint?
The proof reconstruction process
The processing flow must allow the attribution proof to be reconstructed step by step. The initial step consists of identifying the partner, the associated campaign, the specific link, and the code used for this purchase.
Next, you must check the UTM logs, the cookie, the source channel, and the validity duration at the time of the click. It is crucial to compare this with your global attribution model to see whether the criteria are met or not.
If the sale was canceled or subject to a return, the attribution must not be generated, which must be explicitly indicated. You can then choose to manually correct the situation in the system, refuse with detailed proof, forward the case for review, or document the decision to avoid future double requests.
Which examples should you use in your answers?
The importance of concrete and clear cases
Using specific examples helps to de-escalate the situation for the partner. You can say: "The order arrived after the attribution window provided by the program," which shows that the rule is respected but inapplicable in this case.
Another relevant example would be: "The partner code was not used, but we are checking the shared link to see if a redirection was made." This shows your willingness to investigate while reminding them of the technical procedure.
The response must always explain the underlying rule and not just settle for a "no" or "yes". The tone should be educational so that the partner understands why the sale is attributed, rejected, or remains pending, transforming a rejection perceived as unfair into a technical clarification.
When should the file be transferred to the advanced teams?
Identify cases requiring expert intervention
Escalation to a higher hierarchical level is necessary in specific situations such as a strategic partnership or a particularly high commission where the financial stakes justify a manual review.
It is also the time to escalate if there is a direct conflict between multiple partners on the same order, if the evidence provided contradicts system logs, or in case of suspicion of complex fraud.
The bot must transmit all relevant data: partner name, order number, link and UTM code, submitted proof, contested rule, amount involved, and risk level. This allows the specialized team to act quickly without having to contact the partner again for details that are already available.
Which indicators should be monitored to measure the health of the program?
Data-driven support management
To assess the reliability of your attribution system, you must track key indicators related to disputes and corrections. The number of disputes received over a given period is a strong signal.
Also track the rate of manual corrections you perform: if it is high, it means your automatic rules do not cover all legitimate cases or that they are too restrictive. Recurring UTM bugs and partner conflicts must be tracked to identify flaws in your technical setup.
Finally, measuring validation times and partner satisfaction rates after a resolved dispute gives you a view of the overall user experience. This data shows whether your program is perceived as reliable and fair by those who fund it.
What critical mistakes should be avoided in dispute management?
Pitfalls to avoid under pressure
The most common mistake is to correct an attribution without leaving a trace, which makes future auditing impossible and creates accounting liabilities. You must always document why and when an exception was made.
It is also forbidden to promise a commission outside the program rules to appease a frustrated partner, as this creates an unfulfilled expectation for others. Likewise, refusing an attribution without explaining the precise technical criterion leaves the partner in the dark and fuels mistrust.
Failing to report an actual tracking bug to the technical team is also a serious professional error. Attribution must remain verifiable at every stage to maintain partner trust and the store's financial rigor.
How does Qstomy help secure UTM attribution?
Qstomy's AI at the Service of Precision and Follow-up
Qstomy stands out by connecting its AI agent directly to product catalogs, discount bundles, and order history to respond with unmatched precision on attribution cases.
Our solution allows the chatbot to be linked to customer conversations, product files, and partners' specific attribution rules, thus facilitating an immediate response based on system reality. The AI can verify if a UTM code has been correctly applied or if a used or defective product was purchased, preventing calculation errors.
The Qstomy chatbot helps reconstruct the attribution rule and guides the team toward a validated exception without inventing fictional compatibility. It also manages escalation processes for complex cases, while optimizing conversion and average cart value thanks to its contextual understanding of customer needs.
What checklist should be applied before closing a dispute?
Essential steps to validate the resolution
Before providing a final answer to the partner, ask yourself these essential questions. Have you thoroughly checked the UTM link, the cookie, and the interaction date against the attribution window? Is the proof provided sufficiently linked to your program rule to justify an exception?
Has the sale status (return, cancellation, payment) been properly taken into account according to your priority model? Have you manually tracked any correction made to the attribution system? Finally, has the partner clearly understood the technical rule that applies to their specific case?
In short, make sure the response explains why the sale is or is not attributed, and that the chatbot's limit is respected: it reconstructs the rule but escalates high commissions or suspected fraud to the human team. Once these points are validated, the decision can be communicated with firmness.
To go further: Contested UTM attribution: explaining rules to partners without turning every sale into a debate - Qstomy, Integrating customer service responses into an e-commerce SEO strategy helpful to customers - Qstomy, Expired cart: explaining what can be recovered and what cannot - Qstomy, How to handle customer questions when mixing multiple languages in a conversation - Qstomy, Pre-order by variant: explaining why one color or size is available later than another - Qstomy, Name error on an order: correcting what can be corrected before the package gets stuck - Qstomy, How to respond to customers arriving with an affiliate offer - Qstomy.
Enzo
September 3, 2026
