Add Friendly Output for Facebook Data Processing Options Parameters

[jaredrileysmith]

Is your feature request related to a problem? Please describe. It would be nice if there was a section for Facebook events for Data Processing Options, which were only added to the Facebook pixel events ~60 days ago.

Describe the solution you'd like A section for Data Processing Options that contains friendly names for the dpo, dpoco and dpost parameters (which are currently being displayed under the Other section (e.g. dpo = Data Processing Option, dpoco = Data Processing Option - Country and dpost = Data Processing Option - State)

Describe alternatives you've considered The only alternative I've considered is educating paid social managers on how to read/interpret the Data Processing Options as displayed currently.

Additional context Facebook documentation for Data Processing Options https://developers.facebook.com/docs/marketing-apis/data-processing-options/

Screen shot of current display of Data Processing Option parameters in Omnibug

Screen shot of the Data Processing Options displayed in the Facebook Pixel Helper

I am willing to do the development for these changes, but would like input on the usefulness, etc. of the changes. I was also wondering the best way to potentially display information regarding the meaning of the various parameter values. For instance, a value of 0 for the dpoco and dpost parameters instructs Facebook to geolocate the user (and apply the Data Processing Options to California users), but the parameters can be manually set to force the Data Processing Options, etc. I'm not sure if that makes sense, but I would like to see a means of referencing what the parameter values mean in terms of applying the Data Processing Options to Facebook events (anecdotally, the raw parameter values are confusing for many channel managers who are trying to validate their Facebook events and the enhancement would be an improvement over what the Facebook pixel helper offers). Please let me know your thoughts, I am eager to help.

[MisterPhilip]

You know, this is something I've thought about for a while now and I'm still very conflicted on. Adding value lookups/transformations could get very unwieldy, especially for things like this where new rules/laws are put into place and the value might update often. At the same time, it can provide a lot of value to the end user.

In the past, we've transformed raw timestamps into human-readable format but were a little overzealous in which parameters we did it for and started capturing visitor IDs and such (see: #11). So, we'll need to make sure we avoid doing that, but easy enough when we're just adding formatting one-by-one.

If we move forward with it, we'll want to add another option/setting to turn this feature on and off. I imagine we'd also want to keep the raw value in parenthesis, similar to when you hover over a key name and we say Data Processing Options (dpo).

@johndavidsimmons - what are your thoughts on this?