WordPress Server Side Integration

Hi

I try integrating Pirsch with my WordPress setup. I installed the plugin, I have a dashboard and I created a client. Here’s where I cannot seem to make it work.

The Server Side guide tells me I should copy the secret key. OK.
The WordPress guide has a screenshot that doesn’t match the latest plugin UI.

  • I don’t have a hostname or base URL field.
  • I have a dashboard.
  • I created a Client.
  • But now what? The guide says copy the client ID and/or secret.

So which one should I copy where? This is where the guide is confusing to me. In the dashboard settings I don’t see a Client ID anywhere. Where do I get it? Is it the dashbaord ID? Please name it respectively in the doc and plugin or the Dashboard.

Currently I entered the dashboard ID and Client Secret into the plugin. Nothing else. The guide says it now should work and start collecting data.

It doesn’t work, nothing is tracked.

Update: Ah, I removed the Client ID. Now only using the Secret Key. Now it seems to work properly. It would be nice to see this confusion updated in the Docs → If you use Access Token, ONLY copy the Client Secret, that’s it.

On a GDPR note: If I embed your Pirsch JS from your servers on my site, what implications does this have? Do I need to use a cookie banner to block the loading of this script until “statistics” cookies are turned on? I know it’s not setting cookies but there needs to be a consent to load data from remote servers, correct? Some kind of click to accept sending your data to a third party.

Thanks in advance.

Hi Chris,

Sorry for the confusion, our plugin definitely needs an update :slight_smile:

No, we’re GDPR-compliant by default. Consent is required if the third-party side processes the data in a non-GDPR-compliant way, like when extracting personal information. We don’t do that, so you’re fine.

Otherwise, any CDN (content delivery network) would be illegal and half of the internet would be broken. I would still recommend adding a passage to your privacy policy:

Thanks for the clarification Marvin! GDPR is really hard to navigate. Everybody has a different opinion, even lawyers :-/

But your explanation makes sense. The web would be broken!

1 Like