Hi @CampaignerForLife, On the Project key you should put the Server Key, as is used for authenticating push notifications requests with Fire Based Messaging.  It is located under Project Settings>Cloud Messaging within your Firebase Console. As @Craig_Thonis , said the error you are experiencing typ...

HI @raininglemons , You are facing this problem because Adobe Campaign doesn't recognize  the temporary schema 'temp:subworkflow-jumpin'. To secure that data from the subworkflow can be used in the parent workflow I share with you some possible steps to solve the issue:-Be sure you select the nms:re...

Have you tried to isolate parameter 1 and parameter 2, test the behavior verifying that parameter 1 exists under Customer Personalization schema inside Administration> Configuration> Data Schemas.Additionally you can check xpath evaluation by doing the following and see how it behaves: <input label=...

Try with this one:<container type="visibleGroup" visibleIf="EV([../@customSubChannelType], 'Other')"><container label="Personalization value details" type="frame"><static>Please fill Personalization details here.</static><container><input label="Has Personalization?" xpath="../Other/@hasPersonalizat...

Hi @hprice20, I would check for active workflows inside the tool and verify event triggers and services subscriptions inside the part of services. Additionally it is necessary to dissable SMS- related external accounts inside the Administration part of the tool.After doing this if the problem persis...

Hi @MANDM123, I exlain to you the different roles you are asking :Administrators Role: Someone that has full acccess to all the system, configurations and permissions.Deliverability Role: Takes care of email deliverability, optimization and monitoring like managing email metrics, email bounces, blac...

Hi @Sujith_02kumar, I think that the problem comes when relying on EV(), I would recommend you to try substituting it by applying visibleIf condition only to each imput.Here I share an example of a possible imput solution:<input label="Parameter2" visibleIf="[../Other/CustomPersonalization/@Paramete...

Hi @PSNe, The issue appears to be related to how targetData attributes are managed in the submitDelivery API. I share with you some possible solutions:*Check that the targetData includes the correct and required attributes.*Check that the personalization block is configured to handle the targeData a...

Hi @o_X,  I think you can try to do it via the FDA connector, being sure that you not overload campaign system.A possible workaround can be to design a workflow in which you store the necessary data from the broadlogrcp table and configure and export activity to write the data via de FDA connector. ...

Good morning @Adobe_WanKenobi, There isn't a built-in-feature that automatically limits audience targeting to just one customer per postal address after the audience has been created. As a workaround, what you can try is to create a rule that picks one profile per address, using computed filters or ...