Allow event name overrides

[tombennet]

As far as I can see, there is no easy way to override the event name in the payload which is sent to Braze (i.e. it's always taken from the common event data). Attempting to override it using the Additional Event Mapping Options just creates an event_name key in the properties object.

Would it be possible to add an override option? See my attached example.

Thanks!

[adatzer]

Hi @tombennet ! Thank you for the suggestion and the pull request!
This is definitely a configuration option we can add to the next release!
From what i can see, the intention is to set the event_name to a constant value (or to the value of a gtm-ss variable). Could you please share a bit more about the use case? For example, do you think this is an advanced feature or does it enable a rather common use case?

[tombennet]

Hey @adatzer. I suspect this may be useful to a lot of users - our use-case is setting the event_name to a gtm-ss variable lookup table. This table maps the incoming event names used across vendors to the specific naming conventions we use in Braze (e.g. sign_up -> new_user).

Having this field means we can have a single Snowplow/Braze GTM tag in our server-side container, set to fire on all events we want to pass to Braze. Each time it fires, it queries the lookup table and uses the correct Braze event name for the current event. Does that make sense?

[adatzer]

Hey @tombennet !
Thank you very much for sharing more information. It definitely makes sense, so we have included this as the new feature for next release (#12)!

[adatzer]

Closing this PR as v0.3.0 is released allowing event name overrides!
Big thanks @tombennet once again!