What exactly is your use-case?

This is not possible right now with the already published package that we have (see https://www.adobe.io/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/aem/aem_skyline_install.md). One thing that you could do is extend the package as per your needs.Having said that, we are...

When I posted my debug results, I included a snapshot of both the request and response tabs (see below for a better image). That's where you see the difference of headers. But looking at your traces, it seems that the events are being delivered just fine. Regarding the slack integration, I did not t...

Great! Thanks for confirming.

Thanks for sending the details @jgrubbs. We did have an issue at our end in processing triggers. The problem is now resolved. Could you please confirm if it's fixed at your end also?

There is definitely no latency at our side for the Journaling API, but to be doubly sure, could you help us with the IMS organization id and the journaling endpoint for debugging? I can go through our Splunk logs and verify if things are working correctly.

I am not sure what's going wrong at your end. Could you please check what you are getting in the Debug Tracing tab of your console integration (created in step 0). The tutorial has been coded to respond with a simple "pong" message for every event delivered to the webhook, so I don't see any issue h...

If the CLIENT_SECRET is correctly configured, then can you add some logs here and see what exactly is going wrong. I am unable to reproduce the issue on my end. You can see the logs in Glitch by clicking on Tools > Logs.As a last resort, can you try and uncomment the signature verification part to s...

Hi @jasonhampleman: The error that you are encountering is because of a signature mismatch as mentioned in step 2 of the tutorial. However, since you are using Glitch, can you please make sure that the .env file is properly populated, because when you click on "Remix this" it resets the .env file se...

I am afraid there is no short-term solution for the scenarios you mentioned. We do have the feature of "counting events in a journal" in our backlog, but it's not prioritized in our short-term roadmap.