Unable to add data to propositionVisitor schema using the storage option in offer space | Adobe Higher Education
Skip to main content
S
SankarRa1
Level 2
January 31, 2025
해결됨

Unable to add data to propositionVisitor schema using the storage option in offer space

  • January 31, 2025
  • 1 답변
  • 921 조회

Hi All,

 

I am attempting to store contextual data within the propositionVisitor schema or, if feasible, the Visitor schema using the storage feature available in the offer space. Please see the attached screenshot for further details. Could someone confirm whether storage is possible for Visitors, or is it restricted to identified recipients only?

I have extended both the interaction and propositionVisitor schemas to include new attributes, and I can successfully use these attributes for offer eligibility. Offers are being proposed successfully following this configuration without any errors.

 

 

Thanks

Sankar

최고의 답변: ccg1706

Hi @ccg1706 ,

Once again, thank you for following up on this query, I will give more context on current setup and this could help us both in troubleshooting this issue,

Currently I have an offer setup for unitary interaction (web channel) for anonymous customers (Visitors). As I mentioned earlier, I am using the storage option in offer space to store data in propositionVistor schema.

I am currently trying to hardcode this value for testing purpose expecting to load this data to propositionVisitor each time when an offer is proposed. PFB the screenshot for your reference.

I do not have any workflow setup or filters currently in place, still on proposition generation the value is not getting added to the schema.

 

Thanks

Sankar

 


Hi @sankarra1,

 

Don't worry, more than happy to follow up. I share with you possible steps that you can follow to sort it out:

-Check that the right schema is mapped and storage is enabled in the offer space sttings

-Manually try to add a test entry via a workflow or xtk.session.write to check if propositionVisitor accepts data

-Make sure that proposition storage isn't disabled or is getting purged

-Run a workflow with the offer engine with an update activity to force a write into propositionVisitor

-Revise the logs and run SQL queries to check if anything has been inserted into propositionVisitor

-If all this does not work, create a new test offer space mapped to a new schema to see the behavior. Sometimes offer spaces, have weird behavior issues.

 

Let me know how it goes, and if not we will keep digging on it.

 

Regards, 

Celia

1 답변

ccg1706
Community Advisor
ccg1706Community Advisor
Community Advisor
February 1, 2025

Hi @sankarra1,

 

The storage in propositionVisitor is possible whereas the storage in visitor depends on the identification:

If we are talking about an anonymous visitor AC normally does not support storage in the Visitor schema.

On the other side if the visitor is identified, somehow linked to a recipient, storage might be possible, but the best practice is to store persistent data in the Recipient schema rather than in visitor as an alternative.

Finally with the offer space limitations, the way to store contextual data depends on whether the visitor is identified, as propositionVisitor it seems to be designed to track offer interactions rather than store long term visitor data.

 

Here I leave you with some additional documentation links:

Collecting all visits 

Creating offer spaces 

 

Hope it helps.

 

Kind regards,

Celia

 

S
SankarRa1작성자
Level 2
February 1, 2025

Hi @ccg1706 ,

 

Thank you for your response, I am primarily looking to save some contextual info in propositionVisitor schema, but with the current setup as provided in the screenshot , no values are getting saved in the "lastpage" attribute of propositionVisitor schema. Am I missing something?

 

Thanks

Sankar

ccg1706
Community Advisor
ccg1706Community Advisor
Community Advisor
February 1, 2025

Hi @sankarra1,

 

Thanks for coming back again, let me share a few things to check:

-Secure that you are setting the lastpage attribute at some point in your workflow, for example taking a Java Script activity.

-Once the schema is updated double check that the schema has been updated and published.

-Review your filter and workflow conditions, sometimes filters might stop the value from saving.

-Make sure that you store the value when the visitor data is available.

-Also revise the logs for more details, just in case.

 

Let me know if this helps.

Regards, 

Celia

    약관 및 조건Accessibility statement

    Loading footer...