Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Adobe Campaign Classic v6/7 VS Adobe Campaign Standard

Avatar

Avatar
Validate 1
Level 2
johanna_m
Level 2

Likes

13 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
johanna_m
Level 2

Likes

13 likes

Total Posts

7 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
johanna_m
Level 2

12-02-2019

Hello,

I am looking for a comprehensive list of the differences of ACC and ACS, being the two different products, ACS is managed and serviced by Adobe oncloud and ACC can be onpremise, hybrid or fully managed.

However, in terms of the features that have been streamed from ACC, there is nowhere I can find a comprehensive list of the differences between Classic and Standard. can someone enlighten me.

Message was edited by: Johanna Marin
Changed title

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 5
Level 4
AbdulZa
Level 4

Likes

43 likes

Total Posts

50 posts

Correct Reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile

Avatar
Boost 5
Level 4
AbdulZa
Level 4

Likes

43 likes

Total Posts

50 posts

Correct Reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 25
Boost 10
Boost 1
View profile
AbdulZa
Level 4

12-02-2019

I recommend you request a demo of both products from Adobe. They're similar in certain aspects but quite different in others. Having a demo will help you a lot.

Here are few based on recent experience

ACC

- Can be deployed full cloud or hybrid. Hybrid is the common implementation

- Access to the Adobe campaign (CM) system tables in the hybrid deployment (believe me this is very helpful)

- More customizable.

- RT events (trigger messages) has no access to the recipient table.

- Supports inbound and outbound APIs

- Nicer interface but has a lot of features/options (maybe overwhelming for some)

- Thin-client based

- More admin work from maintenance, less ETL development since the admin is mapping existing DB tables as new data schema,

- Performance is as good as your DB server (hybrid installation)

- Both single-threaded when workflows run

- Similar limitations exist in both

- Limited new features in future roadmaps (focus in the future more on ACS)

ACS

- Full cloud deployment only.

- Don't have access to the Adobe campaign (CM) system tables

- Less customizable.

- RT events (trigger messages) has access to the recipient table, can reference recipient attributes for message personalization

- Supports inbound APIs only.

- Fewer options in the interface (Good/Bad)

- Browser-based

- Less admin work from maintenance, More ETL development since the admin is mapping & building the technical workflows to load the data from different data sources.

- More new features in future roadmaps

Thanks.

Answers (0)