Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get the offer in We-Retail page #8

Open
brunob15 opened this issue Apr 2, 2020 · 4 comments
Open

Unable to get the offer in We-Retail page #8

brunob15 opened this issue Apr 2, 2020 · 4 comments
Assignees

Comments

@brunob15
Copy link

brunob15 commented Apr 2, 2020

Hi!

I completed all steps in the tutorial but I'm not able to see the message "Hi! It seems you were trying to buy..." when I navigate to we-retail.

I get the trigger executed, my webhook is properly called and the user profile is properly updated through Target API from my webhook.

This is the batch being sent from the webhook to Target API:

pcId,mcId,trProducts,trPrices,trLink,trThumb,trOffer,trCoupon
aab5c29b49764e3a8a861904a47bf291.17_0,85873594577024071332555981770939565448,Some shorts,39,http://localhost:4502/content/we-retail/us/en/products/men/shorts/slot-canyon-active-shorts.html#mehisusls-L,http://localhost:4502/content/we-retail/us/en/products/men/shorts/slot-canyon-active-shorts/jcr:content/root/product/mehisusls-l/image.thumbnail.64.transparent.png/1473680881374.png,5,ADBETGT5OFF

And this is what I get when I hit the Target API to get the profile (endpoint ...tt.omtrdc.net/rest/v1/profiles):

{
	"client": "xxx",
	"visitorId": "xxx",
	"modifiedAt": "2020-04-02T16:04:03.078-04:00",
	"profileAttributes": {
		"trCoupon": {
			"value": "ADBETGT5OFF",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"trPrices": {
			"value": "39",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"mcId": {
			"value": "xxx",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"trProducts": {
			"value": "Some shorts",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"trThumb": {
			"value": "http://localhost:4502/content/we-retail/us/en/products/men/shorts/slot-canyon-active-shorts/jcr:content/root/product/mehisusls-l/image.thumbnail.64.transparent.png/1473680881374.png",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"trLink": {
			"value": "http://localhost:4502/content/we-retail/us/en/products/men/shorts/slot-canyon-active-shorts.html#mehisusls-L",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		},
		"trOffer": {
			"value": "5",
			"modifiedAt": "2020-04-02T16:04:03.078-04:00"
		}
	}
}

This is how my audience is set up:

image

And these are the customer attributes:

image

With this configuration I am not seeing the message in we-retail as you can see:

image

But if I change my audience to this:

image

Then I do can see the message:

image

Any clue on what could be going on here? Something I could be missing?

Thank you!

@sarahxxu
Copy link
Contributor

sarahxxu commented Apr 8, 2020

@hirenoble could you take a look?

@brunob15
Copy link
Author

brunob15 commented Apr 8, 2020

@brunob15
Copy link
Author

brunob15 commented Apr 13, 2020

Did you have to create customer attributes (from a csv file) in order to have the visitor profile attributes available in Target? I did that because otherwise I could not see any of them here:

image

Coming back to my original question, why could Target not be finding the profile attributes if I see them from Target API by sending the pcId to endpoint .tt.omtrdc.net/rest/v1/profiles/? I'm still facing that issue.

Thank you! @hirenoble @sarahxxu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants