SQL Server BULK IMPORT Truncation error
The import worked for me with your sample data.  But if the real data has commas in that &quot;jsonT&quot; column, it's going to get the data in the wrong columns.  BULK INSERT interprets that comma as part of the CSV format, and then starts putting everything after it in the last column (ClientIPAddress):

If you have control over the creation of the file, you could use a different FIELDTERMINATOR, like pipe (|).  You'll need to pick something that you're sure won't be in the source data, per the docs:

To be usable as a data file for bulk import, a CSV file must comply with the following restrictions:

Data fields never contain the field terminator.
Either none or all of the values in a data field are enclosed in quotation marks (&quot;&quot;).


UID|customerID|DateT|TypeID|AssociatedID|AttributeID|LandingPage|jsonT|ClientIPAddress
9150|2345|2020-09-01T00:00:36Z|1||859|campaign01.html|{'product': 'string01', 'type': '', 'string011'}|192.168.200.2
9151|2356|2020-09-01T00:02:30Z|1||640|campaign02.html|{'product': 'string02', 'type': '', 'string022'}|192.168.200.1

Then your BULK INSERT statement looks like this:
BULK INSERT dbo.activity
FROM 'C:\temp\activity.csv'
WITH (
    FIRSTROW = 2,
    FIELDTERMINATOR = '|',
    ROWTERMINATOR = '0x0a',
    BATCHSIZE = 1000,
    MAXERRORS = 2
);


If you don't have control over the creation of the export file, you'll unfortunately need to:

do some custom pre-processing on it to be able to use it with BULK INSERT
use a different import technology