What's the barrier that is preventing this functionality from being
enabled? It is preferred for us in many instances to go with recurring
deliveries as it is difficult to be restrained by the single send option
in the likely event that we send a particular email on several occasions
to different audiences, but we forego profile substitution as a
Thanks for that, could you please outline what would need to be in a
workflow in order to achieve this. Would it be a matter of querying the
delivery and performing an update data step on it? Could you also please
let me know how I would go about raising an enhancement request?
Hi, when I try to move a workflow from one campaign to another, the
delivery does not move alongside it. I cannot go into the delivery and
move it across as the option is greyed out. Why is this the case and
what can I do to resolve this?
Being able to send proofs using the real data passed through via the
workflow would eliminate a pain point in Adobe Campaign. There is no
real way to test personalisation fields using temporary file data
without running the email as an actual send.
Hello, thanks for your reply. I have tried this and have not gotten it
to work. If I load a list containing with additional data in the
workflow to be passed through and want to test it, by letting the
workflow run as you suggested it runs it as an actual send. This is
really not ideal as I would like to preview this based on data coming
from a file containing actual contacts. I do not have the option to
prepare the delivery for send to test it as a proof using profile
substitutions. Running the...
Hi, I'm trying to proof an email that exists in a workflow based on a
real profile using the new profile substitution functionality. However,
I keep seeing the message below preventing me from doing so. There is no
prepare button and the workflow is started (albeit paused so that I
don't actually send this email to people without first proofing it like
I'm trying to do):Any advice would be much appreciated.
Could there please be a dimension for Adobe Campaign program labels and
IDs in Analytics - that way all campaigns relating to a specific program
could easily be pulled in rather than solely relying on the campaign or
delivery label as detailed in the below link.
I think it would be an amazing quality of life feature to add the
ability to tag different deliveries and campaigns. Currently, the
intergration with Adobe Analytics relies far too heavily on the
establishment of naming conventions and it is difficult to adhere to a
particular naming convention among multiple teams and team members
across a large organisation. Having tagging and enabling functionality
to allow segments in dashboards to be created based on these tags rather
than strict naming con...