Link Attribution
Keep Capacitor booking links associated with your partner ID.
Let the SDK build the link
Submit travel context and let Stay22 build the notification's booking URL. It includes your partner ID (aid) and the stored Stay22 session identifier (sid22). Set optional campaign attribution with:
await Stay22.setCampaignId({ campaignId: 'summer-events' });The notificationClicked event supplies the saved booking URL. Do not replace the issued partner ID with your application name. Verify attribution before shipping.
Send a notification yourself
When your app owns delivery instead of the SDK, identify that separate flow with a direct link:
https://www.stay22.com/allez/roam?address=Paris%2C+France&aid=your-partner-id&source=direct&medium=pushnotif_manualKeep the URL on one line. Add checkin and checkout as YYYY-MM-DD, hotelname for a property, or both lat and lng for coordinates. aid determines the partner credited. Use pushnotif_manual for self-sent notifications; reserve pushnotif and product=mobilesdk for SDK-generated traffic.
Stay22 issues sid22; do not invent it. A self-sent link without it can still credit the partner ID but cannot join the SDK session's notification-to-booking history. Your app owns consent, timing, cancellation and frequency limits for notifications it sends itself.