You can use the Target API to create activities Target API v1.0 Your developers could build a process that sets of this api and creates the campaign.

This is a classic clickTracking problem. The page is being forwarded on too quickly for the response to be sent out. The browser can't send it out in time and aborts it. I bet you see this being pretty sporadic depending on how quick the next page is loading. I've used a delay anchor with the clickTracking. Try something like this$('element').click(function (e) { e.preventDefault(); var goingHere = this.getAttribute("href"); /// track events adobe.target.trackEvent({"mbox": "clicked-cta","params": { "param1": "value1"}}); setTimeout(function(){ window.location = goingHere; },500); }); This is using JQuery. Your developers may not use JQuery so they'd have to do something with Javascript. I hope this helps. Let me know if you have any questions. Russ

You can totally use it without having Recommendations. It is an out of the box feature of Target Standard. If you aren't seeing what you'd expect for "Category Affinity" targeting check out this doc on how it populates Category Affinity I've used it on all types of mboxes from global, regional, and raw boxes and it has worked as I've expected. The algorthm that it uses to define favorite can be confusing, so if it isn't making sense you could reach out to CC.

Hi Chris - I should've provided a little more detail. eVars are Adobe Analytics variables that you would have to implement in your Target offers. They would make a request to Adobe Analytics and the data would appear there. We use a simple onClick with javascript or jquery to populate and call the eVar. I can't really provide you with a code sample because or implementation is so custom it wouldn't make sense. Your developers should be able to call the eVar when visitors engage. it would be simi...

Nope. These are to only 3 fields that you can pass data to the Target DB, audit tables. Here is a couple hacks/work-arounds we used.1. Pass more than one parameter in orderId and productPurchasedID. We've passed strings like this "12345677|abcsedee|dfdf123uejjs" into the orderId and then parsed them out on the DW end. ProductPurchaseId can be comma delimited and you could do the same thing once you pull them with an API you can parse them out on the backend. 2. Use A4T. If you are using Analytic...

This is basic statistics. If you flip a coin 100 times you could potentially get lopsided heads or lopsided tails. If you continue to flip a coin a million times you should experience a close 50/50 percentage of time and the more times you flip. You can tell when an a/b test has normalized and the noise of adding a new experience has leveled out when your experiences come back to an even split. This is the principal behind A/A tests as well. If you run an A/A/B Test you know you can call it when...