Google Convertion Events by Stape Issue "Internal Server Error"

Google Tag Manager Server Container
1

image
image906×718 28.7 KB

image
image2308×523 38.9 KB

Hi everyone,

I’m getting a persistent 500 Internal Server Error when using the Google Conversion Events Tag with the Stape Google Connection (Data Manager API).

The response is a generic text/plain body with just “Internal Server Error” — no JSON error from Google, which makes me think the request never reaches the Data Manager API and fails at the Stape proxy level.

Trace IDs:

  • f458226b-bb85-44fd-8a33-e29f9965407d
  • 80a766b5-c3e0-48c6-a6b3-7a0b8e48417b
  • 8507bbfd-b4bb-453f-b97a-3144586a55da

Since the response is text/plain and not a structured JSON error from Google, it seems like the Stape proxy is failing before forwarding to the Data Manager API. Could someone from the team check the trace IDs above?

Is there anything else I might be missing in the setup? Has anyone else experienced this?

Thanks!

2

Hi Daniele,

  1. Make sure that the target account has a product link; you can check this in Google Ads → Tools → Data Manager
  • If the link isn’t there, here’s the first tip: Make sure the account authorised on the connection has admin rights, if access is via an MCC account – make sure you’re entering the correct customer/operating customer
  • Look for the link in the final (target) account, not in the MCC

Screenshot 2026-02-05 at 18.03.13
Screenshot 2026-02-05 at 18.03.131415×444 92.4 KB

  1. Check that the Terms & Conditions are accepted on the account: Goals → Settings → Customer Data Terms, if not – accept them and try again

Screenshot 2026-02-05 at 18.02.39 (1)
Screenshot 2026-02-05 at 18.02.39 (1)1612×702 102 KB

3

Hi Dmytro,
I just checked, and I can confirm that I can find the link in both the MCC and the subaccount.
The Terms and Conditions are also accepted.
I don’t understand why it’s giving “Internal Server Error” with the convertion

4

@daniele.pikk try adding transaction_id to your tag setup, I assume you’re trying to send signal to Online conversion action, which with DM requires transaction_id for deduplication purposes.

5

Ok thanks for the answer.

I have one last question, i cannot use the API tag for track microconvertion like “add_to_cart” and “begin_checkout”?

For this convertion I don’t have the transaction ID parameter…

6

Think of it is “event_id”, it doe not have to be a order_id.

If you are reporting to an online conversion action though, make sure that said transaction_id is the same in the DM API hit and the normal tag hit. Please refer to the following articles:

1 Like