Hi, The column you're adding to your view is causing the view to perform an inner join against a table that doesn't have data in it.In your web app you need to write this data, alongside the captured recipient data. Thanks,-Jon

Hi, Make a JSSP page with content-type header 'text/calendar' and put a link to it in your delivery. Thanks,-Jon

Interesting. Sounds like drip-style campaign with split prioritization fits the bill then.

Pressure rules are a much more complex pot of stew. Recipient priority you can control with a split after the query.Out of curiosity, what's the business case for the throttling? Is it for this specific campaign or the mta in general?

Sorry, it's js.data, which is the xpath for 'js' or whichever name is given to the js in the wizard. For the rest, object schema is xtk:javascript, table is no, path is /

Hi, Probably an oversight. Just alter the workflow to change it to @successWithoutSeeds.Make sure you also update the snapshot activity at the end. Thanks,-Jon

Hi, Waves are intended for IP warming, which they're not great at either- personalization is done at analysis and can get stale.What you're describing sounds like ordinary continuous deliveries paired with broadlog check in the query, i.e. send to these recipients who are not in the broadlog schema ...

Hi, How do you know which token maps to which phone number? Thanks,-Jon

Hi, You can't import js into personalization blocks, not the normal way. You can:Include another personalization block that has jsInclude the js using the personalization tab of the delivery along with eval(@jsData) in your personalization block Thanks,-Jon

Hi, Yes, use execCommand('curl'). Thanks,-Jon