Data Layer push for beginner

[fern1]

Hey!
here am I with another beginner question..

On the home page of our site, we have a field where the user adds their zip code and the API automatically finds our partner that works in the area. There is no submit button, etc.. Talking with the consulting company that implemented Adobe for us, I was told that we can collect the zipcodes that were added in the field using data layer push. However, they didn't leave any documentation about it or specify how to do so. Since I don't have any experience with the data layer, I'm kind of lost.

Is there documentation that I can read more about this? How would the data layer be for that case?

Additionally, after inserting the zip code, the price of some products automatically appears according to our partner´s price and the user can select quantities of each and move on to the next page. Is there also a way to collect the zip code added, what products were selected, and quantities once they click the next button? I infer this can also be done by data layer push.

And lastly, I saw that it is recommended that we keep a doc mapping out the custom events, evars names, etc.. also so to share with the dev team.. does anyone have a sample doc that they could share so I can have an idea of what has to be done?

Thank you in advance

[leocwlau · Accepted solution]

The consulting company had left you a very big open-ended question on the data layer. It is a big topic on how to implement tracking in the modern approach.

The event-driven data layer (EDDL) is the preferred data layer (at least for me) and you can refer to https://www.searchdiscovery.com/blog/event-driven-data-layer-guide-1/ and https://jimalytics.com/tag-management/the-event-driven-data-layer/ for the idea on how does it work.

Specifically, Adobe has its own Adobe Launch extension implementing EDDL, https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/adobe/client-data-layer/... which you can use directly.

The documentation is always important not only for the dev team to implement the push to the data layer but also to provide the information to users at the end on what metrics and dimensions they should use to create reports. However, the documentation is largely based on your data layer design.