SQL-Task

    

    

 First we have created tow DE Named PushSQL_Userdetails and target DE :




Task 1 - For Gmail User : 


Result after query execution :

3 out of 12 Records fetched


TASK 2 :

Users whose name starts with "A" - 

Query ->


Result after query execution :

                                            2 out of 12 Records fetched

Task 3:

Users whose name ends with "Kumar" -

Query ->


Result after query execution :

                                            3 out of 12 Records fetched



Task 4:

Find users with "sale" in email (campaign filtering)-

Query ->





Result after query execution :

                                            1 out of 12 Records fetched




Task 5:

Find customers from cities containing "pur"

Query ->



Result after query execution :

                                            3 out of 12 Records fetched



Task 6:

Target users with mobile numbers starting with 9

Query ->

Result after query execution :

                                            8 out of 12 Records fetched



Task 7 :

Filter product names containing "Bottle"






Result after query execution :

                                            1 out of 4 Records fetched


Task 8 :

Journey re-entry check (email pattern) :

Query :




Result after query execution :

                                            5 out of 12 Records fetched




Task 9:

Identify test records :

Query ->


Result after query execution :

                                            3 out of 12 Records fetched



Task 10 :

Domain-based segmentation (Yahoo users):

Query ->




Result after query execution :

                                            3 out of 12 Records fetched


Task 11 :

Exclude Gmail users :

Query ->




Result after query execution :

                                            9 out of 12 Records fetched


TASK 12 :

Exclude unsubscribed users :



Result after query execution :

                                            10 out of 12 Records fetched



Test 14 :

Exclude "test" data : -

Query :


Result after query execution :

                                            9 out of 12 Records fetched except test data..


Task 15 :

Exclude specific domain for example : Internal.com

Query :




Result after query execution :

11 out of 12 Records fetched except specific domain given on query.



Task 19 :

Exclude inactive users (last 90 days)

Query : 



Result after query execution :

8 out of 12 Records fetched





Task 13, 16,17,18,20  are not done due to not getting the concept  or logic.





 


































Comments

Post a Comment

Popular posts from this blog

List Assignment

Image
                                                                                                    List Assignment Task 1: Create a New List in SFMC Fist we created the List Named Push_ Monthly Newsletter Subscribers. Defined the below fields : Subscriber Key (Primary Key) Email Address First Name Subscription Status (Active/Inactive) Task 2: Import Initial Data Now need to import the data into this List. Now Import data completed and Data added Task 3: Update & Add New Subscribers: Add new and Update Existing Subscribers Only Verify that: Mark’s Subscription Status is updated to ‘Inactive’ Ethan’s Subscription Status is updated to ‘Active’ Emily is added to the list (since we chose ...
Read more

SQL-Automation Query

Image
 For SQL Query Automation :  Select - Journey Builder > Automation Studio > New Automation  Select : Starting Source Schedule  and drag it to Starting source and drag SQL Query . click on choose and select : Create new Query Activity - Name the Query Write the Query on editor and validate the Query syntax  and also create the New target data extension before moving ahead with all fields. Now select the target data extension with action data as overwrite : Then finish and save and name the Automation: Now Save and Run Once the automation : Click "Select All activity" and Click on Run Click on RUN ONCE Query Automation Run successfully. checked the Targeted DE found all the records are successfully updated.
Read more

SQL_Joins

Image
                                                                                                        JOINS JOIN in Salesforce Marketing Cloud In SFMC, a JOIN is used to combine data from multiple Data Extensions (tables) using a common field. In Salesforce Marketing Cloud , data is usually stored in multiple Data Extensions (DEs) instead of one single table. JOINs are important because they help combine related data from different DEs using a common field. Why JOINs Are Important Without JOINs: 👉 data remains separated reports become difficult personalization is limited segmentation becomes hard JOINs help marketers connect subscriber data, order data, journey d...
Read more