Request Delay power-up

The Request Delay power-up lets you postpone incoming sGTM events by 1 to 1,500 minutes before they’re processed. Use it to align conversion timing with attribution windows, avoid duplicate or premature data, and schedule data submissions around campaign or business hours.

Request Delay is available on the Business subscription plan and higher. To check your current plan or upgrade, go to your sGTM container settings.

How to set up Request Delay

1. Log in to your Stape account and select your sGTM container from the dashboard.

2. Go to the Power-ups tab.

3. Click Use next to the Request Delay panel.

4. Toggle the Request Delay switch to enable it, and click Save changes.

5. Send requests using the following URL format:

https://{sGTM domain}/stape/delay/{minutes}/{path with or without query string}

Where:

• sGTM domain - your tagging server URL, for example: https://ss.example.com.
• minutes - delay duration between 1 and 1,500 in minutes.
• path - the original request path.

Request headers, body, and cookies are forwarded unchanged.

Example: https://ss.example.com/stape/delay/15/

Testing

Send a request using the delay URL format described above, then open Logs in your Stape dashboard. Confirm that the request appears after the specified delay time.

Use case

A sample scenario is an eCommerce team that fires purchase events to GA4 via sGTM at the moment of checkout, but their payment provider sometimes takes several minutes to confirm a transaction. Because of this some conversions are reported before the order is actually valid. GA4 and Google Ads show inflated conversion counts, and ROAS figures are distorted because cancelled or failed orders are being attributed as completed purchases.

You can identify this problem and fix it this way:

1. Confirm the average time between checkout submission and payment confirmation in your payment provider's logs.
2. Modify the request path in your Data Tag or GA4 event tag to include the delay, for example, change /g/collect to /stape/delay/30/g/collect. Enable the Request Delay power-up in your Stape container and save the changes.
3. Place a test order and check Logs to confirm the request arrives approximately 30 minutes after checkout. Cross-reference the delayed event timestamp against the payment confirmation timestamp in your provider's dashboard.

Monitor your payment provider's cancellation and failure data against GA4 conversion counts over 1-2 weeks. If the timing mismatch was the root cause, you will see the gap between reported conversions and confirmed orders narrow, and ROAS figures will begin to reflect actual revenue more accurately.