@arpan-garg Without going into much detail, the key aspect in B2B version is the ability to include "companies, account & one to many relation". I would suggest as a first step audit and list all the possible identities and decide on the one to be used, followed by data ingestion ( the account data ...

@Sindhe Data prep may not be right option here, assuming this profile dataset is not ingested on daily basis. Data prep runs only during data ingestion. One way i would think of doing this is set a ageAsOfToday field in the schema Run a query service job (scheduled every night) which updates this fi...

ok, were you able to check data using query service? 

@akhila1 You will have to debug the browser to check if the event did make it to the edge server and got a 200 status.  

@Anuhya-Y This has to be done at sandbox instance level, i'm assuming that the segment in question is present in both sadnbox ( where target is confgured as destination). Assuming both data has same datasets and data, you may have to create it again if not already available in both sandbox  anil 

@mansibedi For your segmentation definition ( and for all segments where you will use adobe analytics dimensions and metrics) the identity used is "ECID", the count of ECID's where "form start event occurred" AND "form submit did not happen".  The output of this segment query will be total profiles ...

@nico9 If this a website and they are ok to implement SDK, You could have them send it either Client side: Via websdk pointing to same datastream Server side:  without any client side code create a http source for the datastream and they could send data from their server directly to AEP instance

@Umamaheswari_Yakkala There is no native feature for this within target ( and not something which is done in AEP segments), This will require a work around to capture the impression of the target activity into the "target profile" and use it later to suppress the offer  here's a great post by brian ...

@MasterLeeman There is an easier way to do this for schemas, you do not need to export it to azure. You can use the API to export schema from one sandbox and import it to another using the relevant end points, refer to docs here.  Also in works is a native feature which will allow to do this in the ...