Introduction
Automated notifications are central to transparent partner communication and rapid response to deviations in partner sales. Affilentra links tracking, commission calculation and billing with role-based notifications. This article describes concretely how merchants and network operators configure notifications for conversion, chargeback and payout, use personalized templates and set up escalation rules for SLA-critical cases.
Why event-based notifications make sense
Event-based notifications ensure that partners and internal teams receive only relevant information: a conversion confirmation for publishers, a chargeback alert for the operations team, or a payout message for the partner. Automation reduces manual work, speeds up issue resolution and creates traceability for billing and audits.
Preparations: roles and access rights
Before creating notifications, review the roles in Affilentra:
- Software operator: manages system, security and integration parameters.
- Merchant: defines product data, terms and notification rules.
- Partner/Publisher: receives personalized tracking links, in-app messages and payout notifications.
Ensure that only authorized roles can create or modify notifications and that templates are stored with auditability.
Step 1 — Select and prioritize events
Define the events that should trigger notifications. For most merchants, at least these three events are relevant:
- Conversion: successful referral, relevant for partner reporting and immediate commission information.
- Chargeback: reversal or cancellation, critical for billing and fraud monitoring.
- Payout: payment to partner, important for traceability and support inquiries.
Prioritize by urgency: chargebacks deserve higher SLA priority than standard conversion notifications.
Step 2 — Channels: Email, Webhook, In-App
Affilentra supports three main channels. Choose the channel based on the recipient:
- Email — suitable for partners and external recipients; use clear subject lines and structured content.
- Webhook — ideal for integrations with CRM, ERP, ticketing or monitoring systems. Ensure authentication (e.g. HMAC) and retry strategies.
- In-App — fast and context-aware for partner dashboards and internal users in Affilentra.
Combine channels for redundant delivery on SLA-critical events (e.g. In-App + Webhook to an incident system).
Step 3 — Create and personalize templates
Use templates to ensure consistency. Key points:
- Set standardized placeholders, e.g. {{merchant.name}}, {{partner.id}}, {{conversion.id}}, {{amount}}, {{payout.id}}, {{chargeback.reason}}.
- Separate subject/headline, body and optional footer for emails. Pay attention to concise subject lines: they increase open rates and reduce support requests.
- Use conditional blocks for details that appear only when needed (e.g. chargeback reason for chargebacks).
Example: Email template for conversion (subject & body):
Subject: Conversion confirmed — Order {{conversion.id}} (Partner {{partner.id}})
Body:
Hello {{partner.name}},
Your referral resulted in a conversion: Order {{conversion.id}}.
Amount: {{amount}}.
Commission status: Under review. Details in the partner dashboard.
Example: Webhook payload (simplified structure):
{
"event": "conversion",
"conversion": {"id": "{{conversion.id}}", "amount": "{{amount}}", "status": "confirmed"},
"partner": {"id": "{{partner.id}}", "name": "{{partner.name}}"},
"merchant": {"id": "{{merchant.id}}"}
}
Step 4 — Webhook configuration and security
When setting up webhooks, consider:
- Endpoint URL: target system, receiving model (POST, JSON).
- Authentication: HMAC signature with shared secret or bearer token.
- Retry logic: configure retries with exponential backoff and maximum attempts.
- Idempotency: send an event ID (e.g. conversion.id) to avoid duplicate processing.
- Test mode: verify the endpoint with test events before going live.
Step 5 — Escalation rules for SLA‑critical cases
For chargebacks or failed payouts, escalation paths should be defined. Practical approach:
- Define SLA windows (e.g. initial response within X hours). Set deadlines internally; communicate only the necessary information externally.
- Create escalation levels: 1. Operations team (in‑app + email), 2. Team lead (email + webhook to ticketing), 3. Incident manager (push or SMS via external service).
- Automate transitions: if no action occurs within the SLA window, Affilentra automatically triggers the next level.
- Log all escalation steps in the audit history for traceability.
Example rule for chargebacks: If a chargeback is detected and not handled within 4 hours, a webhook to the ticketing system is additionally triggered and a notification is sent to the team lead.
Testing, monitoring and maintenance
Regular testing and monitoring are crucial:
- Use staging environments and send test events with different status values.
- Check email delivery rates and the response codes of webhooks.
- Maintain templates centrally: version changes and keep older versions for review.
- Translations: if you have international partners, maintain locale-specific templates.
Practical example: End-to-end process for a chargeback vertical start
1) A chargeback is reported by the payment provider and verified by Affilentra.
2) Affilentra triggers a chargeback event: in-app alert for the operations team + email to the merchant + webhook to the ticketing system.
3) If no handling occurs within the defined SLA timeframe, Affilentra automatically sends an escalation message to the team lead and triggers a push notification to the incident system.
4) After completion, Affilentra documents the result and informs the partner about the final billing outcome.
Best practices summarized
- Granularity: only relevant events to partners, more detail to internal recipients.
- Security standard: signed webhooks and access restrictions for template changes.
- Redundancy: combination of in-app, webhook and email for critical events.
- Test & versioning: make changes in staging first, version templates.
- Operationalization: automate and audit SLA-compliant escalation chains.
Conclusion and next step
Affilentra provides the building blocks to make partner communication automated, traceable and secure across clearly separated roles. With targeted notification templates, secure webhooks and defined escalation paths, conversion information, chargeback alerts and payout messages can be handled efficiently.
Choose the right entry point and configure your notification setup: Choose entry
Next step
Try Affilentra yourself
A unified platform that transparently brings together product provisioning, tracking, conversion validation, commission calculation and payout across clearly separated roles; option for a self-hosted installation with a perpetual license without revenue sharing; merchants retain control over products, terms and promotional materials; partners receive personal tracking links and a transparent payout history.